Re: GNUstep-make and C++ projects...
On 02.03.2008, at 00:42, Helge Hess wrote: I just tried again with gsmake2 and everything works like a charm. The only thing I had to do was setting LD: ---snip--- LD=g++ -include GNUmakefile.preamble include $(GNUSTEP_MAKEFILES)/tool.make -include GNUmakefile.postamble ---snap--- I'm building the tool against two static (C++) libraries and it just works (on MacOSX 10.5 that is). BTW: just added two subprojects and noticed a warning by libtool on MacOS 10.5. Doesn't seem to be critical though: ---snip--- /usr/bin/libtool -static -o obj/libZ1Core.a obj/z1ne_groupdav.o [...cut...] obj/Z1BootstrapNamedProps.o Z1Versit/obj/subproject.o Z1VersitMap/obj/subproject.o /usr/bin/libtool: warning same member name (subproject.o) in output file used for input files: Z1VersitMap/obj/subproject.o and: Z1Versit/ obj/subproject.o (due to use of basename, truncation, blank padding or duplicate input files) ---snap--- Don't know what/why it is, but I thought you might be interested ;-) Thanks, Helge -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
On Mar 3, 2008, at 5:30 PM, Nicola Pero wrote: PS: The variables used to specify C++ and ObjC++ flags in gnustep- make are currently called CCFLAGS and OBJCCFLAGS (eg, ADDITIONAL_CCFLAGS, etc), not CXXFLAGS and OBJCXXFLAGS. Not sure why. If CXXFLAGS and OBJCXXFLAGS are more "natural" to C++ developers, we could set up a new terminology I guess; it would also be nice to be consistent with the new CXX variable used for the C++ compiler (I couldn't use CC there since it's already in use for the C/ObjC compiler). ;-) Oh, yeah, I was just talking about vanilla gmake--those are the variables used by its built-in rules (see gmake -p). I was not too familiar with what gnustep-make actually uses. I guess it doesn't matter, as long as you don't rely on the built-in rules. Sorry for the confusion, and thanks for clarifying this. -Tim ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
>> It would be nice if gnustep-make was to automatically do all of >> this. Not that sure how to decide when to use C++ linking (is it >> when only CC_FILES are non-empty and all the other xxx_FILES are >> empty ?) and how to best automate it. Suggestions from C++ users >> are welcome. > > Wouldn't it be whenever CC_OBJS or OBJCC_OBJS is non-empty? Yes - good suggestion - I implemented it in trunk. :-) Thanks PS: The variables used to specify C++ and ObjC++ flags in gnustep-make are currently called CCFLAGS and OBJCCFLAGS (eg, ADDITIONAL_CCFLAGS, etc), not CXXFLAGS and OBJCXXFLAGS. Not sure why. If CXXFLAGS and OBJCXXFLAGS are more "natural" to C++ developers, we could set up a new terminology I guess; it would also be nice to be consistent with the new CXX variable used for the C++ compiler (I couldn't use CC there since it's already in use for the C/ObjC compiler). ;-) ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
I'll bet that's the problem, sorry for the bother. I'm running 1.13 I'll download the source and give it a shot. Thanks. On Mar 1, 2008, at 5:44 PM, Nicola Pero wrote: Which version of gnustep-make are you using ? You may want to try 2.0.4 (the latest stable release). ;-) ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-make-2.0.4.tar.gz Thanks -Original Message- From: Jiva DeVoe <[EMAIL PROTECTED]> Sent: Sunday, March 2, 2008 12:43am To: [EMAIL PROTECTED] Cc: Helge Hess <[EMAIL PROTECTED]>, GNUstep Developers > Subject: Re: GNUstep-make and C++ projects... Here's the output of that command: $ make CC=g++ messages=yes Making all for ctool LogTest... g++ -rdynamic -o shared_obj/LogTest \ \ -L/home/jiva/GNUstep/Library/Libraries -L/usr/local/lib/ GNUstep/Local/Library/Libraries -L/usr/local/lib/GNUstep/Network/ Library/Libraries -L/usr/lib/GNUstep/System/Library/Libraries -lm /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 If you look there, mine is missing the source.cc in there. Maybe something with my makefile... again here that is: include $(GNUSTEP_MAKEFILES)/common.make CTOOL_NAME = LogTest LogTest_CC_FILES = source.cc include $(GNUSTEP_MAKEFILES)/ctool.make I'm using the debian packages... could it be something broken with those? BTW, I notice I *have* to name my Makefile GNUmakefile... is it possible to just name it Makefile and have it work? On Mar 1, 2008, at 11:10 AM, Nicola Pero wrote: Thanks Jiva here is what I get -- [EMAIL PROTECTED] C++]$ make messages=yes CC=g++ This is gnustep-make 2.0.4. Type 'make print-gnustep-make-help' for help. Making all for ctool LogTest... cd .; \ /usr/GNUstep/System/Library/Makefiles/mkinstalldirs ./obj g++ source.cc -c \ -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 - DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 - D_REENTRANT -fPIC -g -Wall -DDEBUG -fno-omit-frame-pointer -DGSWARN - DGSDIAGNOSE -Wno-import -g -I. -I/home/nicola/GNUstep/Library/ Headers -I/usr/GNUstep/Local/Library/Headers -I/usr/GNUstep/System/ Library/Headers \ -o obj/source.o g++ -rdynamic -o obj/LogTest \ ./obj/source.o \ -L/home/nicola/GNUstep/Library/Libraries -L/usr/ GNUstep/Local/Library/Libraries -L/usr/GNUstep/System/Library/ Libraries -lm [EMAIL PROTECTED] C++]$ And then the tool works. Do you get the same output ? My g++ is 4.1.2. Is your g++ the same version (it looks like from your output) ? Thanks -Original Message- From: Jiva DeVoe <[EMAIL PROTECTED]> Sent: Saturday, March 1, 2008 5:47pm To: Helge Hess <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], GNUstep Developers Subject: Re: GNUstep-make and C++ projects... So, I tried the make CC=g++ and I got: $ make CC=g++ Making all for ctool LogTest... Linking ctool LogTest ... /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 On Mar 1, 2008, at 6:19 AM, Helge Hess wrote: On 01.03.2008, at 12:16, Nicola Pero wrote: make CC=g++ Hm, is there a special CC variable for CPP files? I think I wondered about that. It would be nice if gnustep-make was to automatically do all of this. Not that sure how to decide when to use C++ linking (is it when only CC_FILES are non-empty and all the other xxx_FILES are empty ?) and how to best automate it. Suggestions from C++ users are welcome. I qualify, unfortunately ;-) I also tried using gstep-make (on MacOSX) to compile a C++ project, but failed for reasons I don't remember anymore :-) I think activating C++ linking on non-empty CC_FILES should be OK. However, then CC_FILES should support compilation of .c files using g ++. Eg: CC_FILES = \ a.cpp \ b.c If all that would work as-is on Windows to produce DLLs and such, it would be awesome! :-) Further it would be very nice if one could use the VS C++ compiler instead of g++. But that probably works already (CC=vcc++ or whatever) Hm, sweet. I think I give it another try today and see what was wrong with using gsmake for me. Thanks, Helge -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
On 02.03.2008, at 00:47, Jiva DeVoe wrote: Y'know... I looked at scons a year or so back.. This comment was an exclusive for Nicola ;-) Thanks, Helge -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
Which version of gnustep-make are you using ? You may want to try 2.0.4 (the latest stable release). ;-) ftp://ftp.gnustep.org/pub/gnustep/core/gnustep-make-2.0.4.tar.gz Thanks -Original Message- From: Jiva DeVoe <[EMAIL PROTECTED]> Sent: Sunday, March 2, 2008 12:43am To: [EMAIL PROTECTED] Cc: Helge Hess <[EMAIL PROTECTED]>, GNUstep Developers Subject: Re: GNUstep-make and C++ projects... Here's the output of that command: $ make CC=g++ messages=yes Making all for ctool LogTest... g++ -rdynamic -o shared_obj/LogTest \ \ -L/home/jiva/GNUstep/Library/Libraries -L/usr/local/lib/ GNUstep/Local/Library/Libraries -L/usr/local/lib/GNUstep/Network/ Library/Libraries -L/usr/lib/GNUstep/System/Library/Libraries -lm /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 If you look there, mine is missing the source.cc in there. Maybe something with my makefile... again here that is: include $(GNUSTEP_MAKEFILES)/common.make CTOOL_NAME = LogTest LogTest_CC_FILES = source.cc include $(GNUSTEP_MAKEFILES)/ctool.make I'm using the debian packages... could it be something broken with those? BTW, I notice I *have* to name my Makefile GNUmakefile... is it possible to just name it Makefile and have it work? On Mar 1, 2008, at 11:10 AM, Nicola Pero wrote: > Thanks Jiva > > here is what I get -- > > [EMAIL PROTECTED] C++]$ make messages=yes CC=g++ > This is gnustep-make 2.0.4. Type 'make print-gnustep-make-help' for > help. > Making all for ctool LogTest... > cd .; \ >/usr/GNUstep/System/Library/Makefiles/mkinstalldirs ./obj > g++ source.cc -c \ > -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 - > DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 - > D_REENTRANT -fPIC -g -Wall -DDEBUG -fno-omit-frame-pointer -DGSWARN - > DGSDIAGNOSE -Wno-import -g -I. -I/home/nicola/GNUstep/Library/ > Headers -I/usr/GNUstep/Local/Library/Headers -I/usr/GNUstep/System/ > Library/Headers \ > -o obj/source.o > g++ -rdynamic -o obj/LogTest \ > ./obj/source.o \ > -L/home/nicola/GNUstep/Library/Libraries -L/usr/ > GNUstep/Local/Library/Libraries -L/usr/GNUstep/System/Library/ > Libraries -lm > [EMAIL PROTECTED] C++]$ > > And then the tool works. Do you get the same output ? My g++ is > 4.1.2. > Is your g++ the same version (it looks like from your output) ? > > Thanks > > > -Original Message- > From: Jiva DeVoe <[EMAIL PROTECTED]> > Sent: Saturday, March 1, 2008 5:47pm > To: Helge Hess <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED], GNUstep Developers > > Subject: Re: GNUstep-make and C++ projects... > > So, I tried the make CC=g++ and I got: > > $ make CC=g++ > Making all for ctool LogTest... > Linking ctool LogTest ... > /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function > `_start': > ../sysdeps/i386/elf/start.S:115: undefined reference to `main' > collect2: ld returned 1 exit status > make[1]: *** [shared_obj/LogTest] Error 1 > make: *** [LogTest.all.ctool.variables] Error 2 > > > On Mar 1, 2008, at 6:19 AM, Helge Hess wrote: > >> On 01.03.2008, at 12:16, Nicola Pero wrote: >>> make CC=g++ >> >> Hm, is there a special CC variable for CPP files? I think I wondered >> about that. >> >>> It would be nice if gnustep-make was to automatically do all of >>> this. Not that sure how to decide when to use C++ linking (is it >>> when only CC_FILES are non-empty and all the other xxx_FILES are >>> empty ?) and how to best automate it. Suggestions from C++ users >>> are welcome. >> >> >> I qualify, unfortunately ;-) I also tried using gstep-make (on >> MacOSX) to compile a C++ project, but failed for reasons I don't >> remember anymore :-) >> >> I think activating C++ linking on non-empty CC_FILES should be OK. >> However, then CC_FILES should support compilation of .c files using g >> ++. Eg: >> CC_FILES = \ >> a.cpp \ >> b.c >> >> If all that would work as-is on Windows to produce DLLs and such, it >> would be awesome! :-) >> Further it would be very nice if one could use the VS C++ compiler >> instead of g++. But that probably works already (CC=vcc++ or >> whatever) >> >> Hm, sweet. I think I give it another try today and see what was >> wrong with using gsmake for me. >> >> Thanks, >> Helge >> -- >> Helge Hess >> http://www.helgehess.eu/ >> >> >> ___ >> Gnustep-dev mailing list >> Gnustep-dev@gnu.org >> http://lists.gnu.org/mailman/listinfo/gnustep-dev >> > > > ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
Y'know... I looked at scons a year or so back.. and it's cool and everything... but ultimately... I'm looking at coming back to Make... which is one reason I'm looking at GNUstep make... this may seem kinda like a perversion of what GNUstep make is designed around... but from what I've seen... the whole GNUstep make system is pretty darn complete, and does a really nice job. I started asking myself "why couldn't I use this for just plain old standard C++ projects too?" So thus, I'm kinda poking my nose around in there. On Mar 1, 2008, at 4:42 PM, Helge Hess wrote: PS: or should I move to SCons instead? ;-> ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
Here's the output of that command: $ make CC=g++ messages=yes Making all for ctool LogTest... g++ -rdynamic -o shared_obj/LogTest \ \ -L/home/jiva/GNUstep/Library/Libraries -L/usr/local/lib/ GNUstep/Local/Library/Libraries -L/usr/local/lib/GNUstep/Network/ Library/Libraries -L/usr/lib/GNUstep/System/Library/Libraries -lm /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 If you look there, mine is missing the source.cc in there. Maybe something with my makefile... again here that is: include $(GNUSTEP_MAKEFILES)/common.make CTOOL_NAME = LogTest LogTest_CC_FILES = source.cc include $(GNUSTEP_MAKEFILES)/ctool.make I'm using the debian packages... could it be something broken with those? BTW, I notice I *have* to name my Makefile GNUmakefile... is it possible to just name it Makefile and have it work? On Mar 1, 2008, at 11:10 AM, Nicola Pero wrote: Thanks Jiva here is what I get -- [EMAIL PROTECTED] C++]$ make messages=yes CC=g++ This is gnustep-make 2.0.4. Type 'make print-gnustep-make-help' for help. Making all for ctool LogTest... cd .; \ /usr/GNUstep/System/Library/Makefiles/mkinstalldirs ./obj g++ source.cc -c \ -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 - DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 - D_REENTRANT -fPIC -g -Wall -DDEBUG -fno-omit-frame-pointer -DGSWARN - DGSDIAGNOSE -Wno-import -g -I. -I/home/nicola/GNUstep/Library/ Headers -I/usr/GNUstep/Local/Library/Headers -I/usr/GNUstep/System/ Library/Headers \ -o obj/source.o g++ -rdynamic -o obj/LogTest \ ./obj/source.o \ -L/home/nicola/GNUstep/Library/Libraries -L/usr/ GNUstep/Local/Library/Libraries -L/usr/GNUstep/System/Library/ Libraries -lm [EMAIL PROTECTED] C++]$ And then the tool works. Do you get the same output ? My g++ is 4.1.2. Is your g++ the same version (it looks like from your output) ? Thanks -Original Message- From: Jiva DeVoe <[EMAIL PROTECTED]> Sent: Saturday, March 1, 2008 5:47pm To: Helge Hess <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], GNUstep Developers > Subject: Re: GNUstep-make and C++ projects... So, I tried the make CC=g++ and I got: $ make CC=g++ Making all for ctool LogTest... Linking ctool LogTest ... /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 On Mar 1, 2008, at 6:19 AM, Helge Hess wrote: On 01.03.2008, at 12:16, Nicola Pero wrote: make CC=g++ Hm, is there a special CC variable for CPP files? I think I wondered about that. It would be nice if gnustep-make was to automatically do all of this. Not that sure how to decide when to use C++ linking (is it when only CC_FILES are non-empty and all the other xxx_FILES are empty ?) and how to best automate it. Suggestions from C++ users are welcome. I qualify, unfortunately ;-) I also tried using gstep-make (on MacOSX) to compile a C++ project, but failed for reasons I don't remember anymore :-) I think activating C++ linking on non-empty CC_FILES should be OK. However, then CC_FILES should support compilation of .c files using g ++. Eg: CC_FILES = \ a.cpp \ b.c If all that would work as-is on Windows to produce DLLs and such, it would be awesome! :-) Further it would be very nice if one could use the VS C++ compiler instead of g++. But that probably works already (CC=vcc++ or whatever) Hm, sweet. I think I give it another try today and see what was wrong with using gsmake for me. Thanks, Helge -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
On 01.03.2008, at 14:19, Helge Hess wrote: Hm, sweet. I think I give it another try today and see what was wrong with using gsmake for me. I just tried again with gsmake2 and everything works like a charm. The only thing I had to do was setting LD: ---snip--- LD=g++ -include GNUmakefile.preamble include $(GNUSTEP_MAKEFILES)/tool.make -include GNUmakefile.postamble ---snap--- I'm building the tool against two static (C++) libraries and it just works (on MacOSX 10.5 that is). Next thing would be to move the whole compilation on Windows to gsmake (currently its all VS projects). Maybe next weekend ;-) Thanks a lot! Helge PS: or should I move to SCons instead? ;-> -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
Thanks Jiva here is what I get -- [EMAIL PROTECTED] C++]$ make messages=yes CC=g++ This is gnustep-make 2.0.4. Type 'make print-gnustep-make-help' for help. Making all for ctool LogTest... cd .; \ /usr/GNUstep/System/Library/Makefiles/mkinstalldirs ./obj g++ source.cc -c \ -MMD -MP -DGNUSTEP -DGNUSTEP_BASE_LIBRARY=1 -DGNU_GUI_LIBRARY=1 -DGNU_RUNTIME=1 -DGNUSTEP_BASE_LIBRARY=1 -D_REENTRANT -fPIC -g -Wall -DDEBUG -fno-omit-frame-pointer -DGSWARN -DGSDIAGNOSE -Wno-import -g -I. -I/home/nicola/GNUstep/Library/Headers -I/usr/GNUstep/Local/Library/Headers -I/usr/GNUstep/System/Library/Headers \ -o obj/source.o g++ -rdynamic -o obj/LogTest \ ./obj/source.o \ -L/home/nicola/GNUstep/Library/Libraries -L/usr/GNUstep/Local/Library/Libraries -L/usr/GNUstep/System/Library/Libraries -lm [EMAIL PROTECTED] C++]$ And then the tool works. Do you get the same output ? My g++ is 4.1.2. Is your g++ the same version (it looks like from your output) ? Thanks -Original Message- From: Jiva DeVoe <[EMAIL PROTECTED]> Sent: Saturday, March 1, 2008 5:47pm To: Helge Hess <[EMAIL PROTECTED]> Cc: [EMAIL PROTECTED], GNUstep Developers Subject: Re: GNUstep-make and C++ projects... So, I tried the make CC=g++ and I got: $ make CC=g++ Making all for ctool LogTest... Linking ctool LogTest ... /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 On Mar 1, 2008, at 6:19 AM, Helge Hess wrote: > On 01.03.2008, at 12:16, Nicola Pero wrote: >> make CC=g++ > > Hm, is there a special CC variable for CPP files? I think I wondered > about that. > >> It would be nice if gnustep-make was to automatically do all of >> this. Not that sure how to decide when to use C++ linking (is it >> when only CC_FILES are non-empty and all the other xxx_FILES are >> empty ?) and how to best automate it. Suggestions from C++ users >> are welcome. > > > I qualify, unfortunately ;-) I also tried using gstep-make (on > MacOSX) to compile a C++ project, but failed for reasons I don't > remember anymore :-) > > I think activating C++ linking on non-empty CC_FILES should be OK. > However, then CC_FILES should support compilation of .c files using g > ++. Eg: > CC_FILES = \ >a.cpp \ >b.c > > If all that would work as-is on Windows to produce DLLs and such, it > would be awesome! :-) > Further it would be very nice if one could use the VS C++ compiler > instead of g++. But that probably works already (CC=vcc++ or whatever) > > Hm, sweet. I think I give it another try today and see what was > wrong with using gsmake for me. > > Thanks, > Helge > -- > Helge Hess > http://www.helgehess.eu/ > > > ___ > Gnustep-dev mailing list > Gnustep-dev@gnu.org > http://lists.gnu.org/mailman/listinfo/gnustep-dev > ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
On Mar 1, 2008, at 7:19 AM, Helge Hess wrote: On 01.03.2008, at 12:16, Nicola Pero wrote: make CC=g++ Hm, is there a special CC variable for CPP files? I think I wondered about that. There is CXX and CXXFLAGS. It would be nice if gnustep-make was to automatically do all of this. Not that sure how to decide when to use C++ linking (is it when only CC_FILES are non-empty and all the other xxx_FILES are empty ?) and how to best automate it. Suggestions from C++ users are welcome. Wouldn't it be whenever CC_OBJS or OBJCC_OBJS is non-empty? -Tim ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
So, I tried the make CC=g++ and I got: $ make CC=g++ Making all for ctool LogTest... Linking ctool LogTest ... /usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function `_start': ../sysdeps/i386/elf/start.S:115: undefined reference to `main' collect2: ld returned 1 exit status make[1]: *** [shared_obj/LogTest] Error 1 make: *** [LogTest.all.ctool.variables] Error 2 On Mar 1, 2008, at 6:19 AM, Helge Hess wrote: On 01.03.2008, at 12:16, Nicola Pero wrote: make CC=g++ Hm, is there a special CC variable for CPP files? I think I wondered about that. It would be nice if gnustep-make was to automatically do all of this. Not that sure how to decide when to use C++ linking (is it when only CC_FILES are non-empty and all the other xxx_FILES are empty ?) and how to best automate it. Suggestions from C++ users are welcome. I qualify, unfortunately ;-) I also tried using gstep-make (on MacOSX) to compile a C++ project, but failed for reasons I don't remember anymore :-) I think activating C++ linking on non-empty CC_FILES should be OK. However, then CC_FILES should support compilation of .c files using g ++. Eg: CC_FILES = \ a.cpp \ b.c If all that would work as-is on Windows to produce DLLs and such, it would be awesome! :-) Further it would be very nice if one could use the VS C++ compiler instead of g++. But that probably works already (CC=vcc++ or whatever) Hm, sweet. I think I give it another try today and see what was wrong with using gsmake for me. Thanks, Helge -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep-make and C++ projects...
On 01.03.2008, at 12:16, Nicola Pero wrote: make CC=g++ Hm, is there a special CC variable for CPP files? I think I wondered about that. It would be nice if gnustep-make was to automatically do all of this. Not that sure how to decide when to use C++ linking (is it when only CC_FILES are non-empty and all the other xxx_FILES are empty ?) and how to best automate it. Suggestions from C++ users are welcome. I qualify, unfortunately ;-) I also tried using gstep-make (on MacOSX) to compile a C++ project, but failed for reasons I don't remember anymore :-) I think activating C++ linking on non-empty CC_FILES should be OK. However, then CC_FILES should support compilation of .c files using g+ +. Eg: CC_FILES = \ a.cpp \ b.c If all that would work as-is on Windows to produce DLLs and such, it would be awesome! :-) Further it would be very nice if one could use the VS C++ compiler instead of g++. But that probably works already (CC=vcc++ or whatever) Hm, sweet. I think I give it another try today and see what was wrong with using gsmake for me. Thanks, Helge -- Helge Hess http://www.helgehess.eu/ ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
RE: GNUstep-make and C++ projects...
The easiest solution might be to use g++ instead of gcc to link C++ files.
make CC=g++
works for me.
Presumably the alternative is to get the right C++ linking flags from gcc
and use them ?
It would be nice if gnustep-make was to automatically do all of this. Not
that sure how to decide when to use C++ linking (is it when only CC_FILES
are non-empty and all the other xxx_FILES are empty ?) and how to best automate
it. Suggestions from C++ users are welcome.
Thanks
-Original Message-
From: Jiva DeVoe <[EMAIL PROTECTED]>
Sent: Saturday, March 1, 2008 12:54am
To: gnustep-dev@gnu.org
Subject: GNUstep-make and C++ projects...
Is it possible to use GNUstep-make for just plain old C++ projects
with no other involvement with GNUstep?
I tried making a ctool, and I get linker errors when I try.
My stuff looks like this:
include $(GNUSTEP_MAKEFILES)/common.make
CTOOL_NAME = LogTest
LogTest_CC_FILES = source.cc
include $(GNUSTEP_MAKEFILES)/ctool.make
#include
int main (int argc, char *argv)
{
std::cout << "foo" << std::endl;
return 0;
}
and the error I get is:
Making all for ctool LogTest...
Linking ctool LogTest ...
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function
`_start':
../sysdeps/i386/elf/start.S:115: undefined reference to `main'
collect2: ld returned 1 exit status
make[1]: *** [shared_obj/LogTest] Error 1
make: *** [LogTest.all.ctool.variables] Error 2
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
GNUstep-make and C++ projects...
Is it possible to use GNUstep-make for just plain old C++ projects
with no other involvement with GNUstep?
I tried making a ctool, and I get linker errors when I try.
My stuff looks like this:
include $(GNUSTEP_MAKEFILES)/common.make
CTOOL_NAME = LogTest
LogTest_CC_FILES = source.cc
include $(GNUSTEP_MAKEFILES)/ctool.make
#include
int main (int argc, char *argv)
{
std::cout << "foo" << std::endl;
return 0;
}
and the error I get is:
Making all for ctool LogTest...
Linking ctool LogTest ...
/usr/lib/gcc/i486-linux-gnu/4.1.2/../../../../lib/crt1.o: In function
`_start':
../sysdeps/i386/elf/start.S:115: undefined reference to `main'
collect2: ld returned 1 exit status
make[1]: *** [shared_obj/LogTest] Error 1
make: *** [LogTest.all.ctool.variables] Error 2
___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev
