[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Files that don't belong in CVS
|
At 02:54 PM 2/11/2003, Mark C. Chu-Carroll wrote:
<snip>
The one problem is that I'm trying to move to a build process that
uses the Eclipse build files. If we don't include those, then we make
it impossible for non-Eclipsers to build the system.
It's clearly a problem.
The Bugzilla item #31457 I entered yesterday describes a modified
command-line build process which uses the Eclipse-generated build files.
(Maybe you should look at it :> - see EclipseBuildNotes.html)
Unfortunately -- the presence of platform- and window-system- specific
properties makes the build.xml files dangerous to rely on, UIMHO.
Eclipse can (and will) build jars for a different platform, as dictated
by the 'ws' and 'os' properties (x-platform building is a feature, not a
bug :-)
Perhaps the appropriate thing is to put minimal hand-written build files
into the project directories that *don't* get changed by Eclipse, and
that don't include the platform specifics? In other words, create a
manual build process that parallels the Eclipse one, but doesn't use
the same build files?
I started to write up a semi-ridiculous idea .....
Doh!
Here's a simpler way:
1) use the Eclipse-generated build.xml files, and check them into CVS
for command-line build purposes
2) For command-line builds, override the 'os' and 'ws' properties in the Ant
command line:
$ ant -Dos=CURRENT_OS -Dws=CURRENT_WS
replacing CURRENT_OS with 'linux', 'win32', 'macosx' etc. as appropriate, and
replacing CURRENT_WS with 'gtk', 'motif', 'win32', 'carbon' etc. as
appropriate.
3) For Eclipse IDE builds -- delete build.xml and regenerate a local
version, then
build as usual.
On Tue, 2003-02-11 at 14:43, Jim Wright - IBM Research wrote:
> In the course of generating my recent patches, I tripped over a number of
> files that really don't belong in CVS.
> These include:
>
> Eclipse-generated build.xml files
> (because they contain platform- and window-toolkit- specific
properties)
> All contents of 'bin' folders
> All contents of 'build' folders
>
> The presence of these files complicate patch generation and increase
the time
> it takes to sync with the repository.
>
> I would like to delete them from our CVS repository (and ask committers to
> avoid checking them in in future).
>
> Comments? Votes for/against?
>
--
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
jim.wright@xxxxxxx
