RE: [cdt-dev] Overnight build on managed make projects

["Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>]

I'm just saying the makefile generators weren't built with that in mind.
You're mileage may very. But we do use absolute paths in a number of
places. (which may be decreasing as people fix that).
 
BTW, I also hope people get the sense that the build ship is currently
rudderless. We need to get together as a community and straigthen it out
to gather requirements and make sure the build system meets them.
 
Doug.
 


________________________________

	From: cdt-dev-bounces@xxxxxxxxxxx
[mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of John Camelon
	Sent: Friday, May 30, 2008 11:07 AM
	To: CDT General developers list.
	Subject: RE: [cdt-dev] Overnight build on managed make projects
	
	

	I am curious about this stance! ( I have been trying to setup a
CDT/Rational Team Concert build environment). 
	I would think that with the proper process for merging, it
should not be a problem to share the makefiles. 
	When in doubt, the user would have to regen the makefiles and
mark all conflicts as merged!
	
	2/3 of the pde madness I experience month to month has to do
with the way that we build plugins in the
	IDE differs signficantly from how it builds for a build,
particularly for an environment which supports many targets. 
	The same merge issues exist as they do for makefiles, but they
are more subtle and spread across multiple manifests,
	features, build.properties, etc. Or in CDT's case, the cproject
files, etc.. 
	
	Running eclipse headless on a build machine may be the way to
reach this commonality, 
	but I thought that you could achieve the same thing with the
already existing currency (makefiles). 
	
	--
	JohnC
	
	 "Schaefer, Doug" <Doug.Schaefer@xxxxxxxxxxxxx>
	
	
	

				"Schaefer, Doug"
<Doug.Schaefer@xxxxxxxxxxxxx> 
				Sent by: cdt-dev-bounces@xxxxxxxxxxx 

				30/05/2008 10:49 AM 
	
	Please respond to
"CDT General developers list." <cdt-dev@xxxxxxxxxxx>

 

To

<wieant@xxxxxxxxx>, "CDT General developers list." <cdt-dev@xxxxxxxxxxx>



cc

	


Subject

RE: [cdt-dev] Overnight build on managed make projects	
	 	

	The official stance is that the makefiles generated by managed
make are
	not intended to be checked into source control (which is why
they are
	marked derived) and are not meant to be shared. The fact that
they run
	outside of Eclipse is also not really supported, but as you
mention,
	luckily it works.
	
	There is a bug/enhancement request to support building managed
build
	projects in this manner. Idealy we would use a headless ecilpse
to do
	the build and take advantage of CDT's internal builder and other
	builders where possible, but we have run into some weird
dependencies
	with core components on UI components that is currently
preventing that.
	I don't have the bug number handy but it shouldn't be too hard
to find
	(althought with >1200 open bugs it might be).
	
	Doug.
	
	> -----Original Message-----
	> From: cdt-dev-bounces@xxxxxxxxxxx 
	> [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Wieant
Nielander
	> Sent: Friday, May 30, 2008 10:29 AM
	> To: CDT General developers list.
	> Subject: Re: [cdt-dev] Overnight build on managed make
projects
	> 
	> 
	> >> I have a bunch of projects that were built using managed 
	> make files.  
	> >> I now need to compile these on a standalone box using an
overnight 
	> >> build script.
	> >>
	> >> Is there a plugin or tool that will create standalone 
	> makefiles that 
	> >> I can call from my script?  I tried to use the eclipse 
	> made ones, but 
	> >> they use absolute directories instead of relative once, and
the 
	> >> directory structure on the overnight build machine does 
	> not match the 
	> >> developers directory structure.
	> 
	> > If generated makefile does not work you can enter a bug
report to 
	> > track this issue.
	> 
	> The thing however is that the standard gcc based makefile 
	> does use relative dirs (see below), except for linked 
	> resources that is.
	> Gerald, perhaps you can post some additional info, like the 
	> toolchain you are using and perhaps an excerpt from the 
	> makefile that shows the use of absolute dirs.
	> 
	> 
	> # Each subdirectory must supply rules for building sources it 
	> contributes
	> src/%.o: ../src/%.c
	> @echo 'Building file: $<'
	> @echo 'Invoking: Cygwin C Compiler'
	> gcc -O0 -g3 -Wall -c -fmessage-length=0 -MMD -MP 
	> -MF"$(@:%.o=%.d)" -MT"$(@:%.o=%.d)" -o"$@" "$<"
	> @echo 'Finished building: $<'
	> @echo ' '
	> _______________________________________________
	> cdt-dev mailing list
	> cdt-dev@xxxxxxxxxxx
	> https://dev.eclipse.org/mailman/listinfo/cdt-dev
	> 
	_______________________________________________
	cdt-dev mailing list
	cdt-dev@xxxxxxxxxxx
	https://dev.eclipse.org/mailman/listinfo/cdt-dev