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...
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...
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
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
WildMenus and layering...
I've done some hacking on WildMenus as some of you already know (http://www.random-ideas.net/Blog/19) that said, one of my beefs is that the top menu is always letting windows from the window manager get maximized underneath it. What do I need to do with the code to prevent this from happening? I am guessing that I need to set some kind of special property on the window used for the menu. What I'd like is for it to work like the panels from GNOME etc... so when an app is maximized it does not go behind the panel/menu. Anyone? Thx in advance. ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
WildMenus
Michael Hanni said it was ok for me to go ahead and release my modified version of WildMenus... sooo... here's my announcement on my Blog as well as a link to the tarball.. For those who care - I hacked WildMenus to be more "Mac-Like" and to also allow me to set a single icon in the corner instead of using the Application Icon... Announcement: http://www.random-ideas.net/Blog/19 Tarball: http://www.random-ideas.net/Software/WildMenus-jd.tar.gz I apologize if this more appropriately belongs on GNUstep-announce or something... if someone can point me to the right mailing list, I'd be happy to post it there instead. I just thought since it was kinda at a developer-level thing... and whatnot... perhaps announce wasn't right. -- Jiva DeVoe http://www.random-ideas.net PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: GNUstep ROADMAP
On Nov 26, 2005, at 11:23 AM, Adrian Robert wrote: GNUstep 1.1 Integrate camaelon into gui ... I think this should be in 1.0 as a matter of practicality ... as far as I can see, this is an easily achievable target, so why not do it soon. I really think this needs to go into 1.0. Judging by the amount of discussion themes ALWAYS get whenever there is ANY external publicity about GNUstep, I think initial reception will be far better if we can just say, "download and switch on this theme" instead of "someday we'll have Camealon in GNUstep". Let's not be impatient for the 1.0 release and then have lots of people dismissing it with "great, but too 80's for me".. Integration of WildMenus ... I haven't looked at this, so i don't know, but seems reasonable. This on the other hand, we rarely hear about on the lists, so I think it's a much lower priority than Camaelon. I'm new here, and obviously, much genuflection to everyone involved... but I just wanted to say from an outsider's standpoint, camaelon IMO is an absolute requirement to have in 1.0. I'm sure there's lots of arguments on why not to do it, but from an outsider standpoint, it's a must-have.WRT WildMenus - WildMenus is useful if one is coming from a Mac, and wants Mac style menus... I'd argue that alone makes it worthwhile - but the thing that would make it really killer would be if it could also attach the menus to whatever main window there is currently (ala Windows etc) to make GNUstep apps not look like the "odd man out" when mixing on other window managers/desktops. I know this is not a trivial task. WildMenus - though cool, and I obviously use it myself, I think is not vital for a 1.0. 1.1 sure... when it gets a nice overhaul with a clock and little status applets like the mac menu, or if it gets the ability to do windows-like menus... (:: sounds of screams from GNUstep purists ::) -- Jiva DeVoe http://www.devoesquared.com PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: DO compatibility with Apple DO
H - now that's an interesting idea...But how to differentiate between identically named classes on GNUstep vs Mac OS in the bridge server?Would also be pretty slow too I'd bet.On Nov 26, 2005, at 9:56 PM, Sheldon Gill wrote:Jiva DeVoe wrote: Yeah, the problem is, you'd have to be SURE Apple was using the XML format for all DO operations - and I'd bet you couldn't do that.Oh well.Again, sorry for bringing up a topic that's in the FAQ. Actually, although quite a challenge I think it should be possible get a reasonable degree of inter-operability by installing a daemon on MacOS which will do GDO over the wire and call out to PDO...Regards,Sheldon -- Jiva DeVoe http://www.devoesquared.com PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: DO compatibility with Apple DO
Yeah, the problem is, you'd have to be SURE Apple was using the XML format for all DO operations - and I'd bet you couldn't do that.Oh well.Again, sorry for bringing up a topic that's in the FAQ.On Nov 26, 2005, at 9:01 PM, Nicolas Roard wrote:On 11/27/05, Jiva DeVoe <[EMAIL PROTECTED]> wrote: Fair enough, sorry for asking a Q already answered there.I wonder if the change to OS X 86 + their XML format for archiving holds anynew hope for compatibility... does it? I suppose not. Well, if Cocoa uses XML for DO exchanges, I guess it could be possiblein theory to have a compatible DO between GNUstep and OSX. But Ireally don't know if they use (or can be set up to use) XML instead ofbinary serialization for DO.. could be worth checking.--Nicolas Roard"Any sufficiently advanced technology is indistinguishable from magic." -Arthur C. Clarke -- Jiva DeVoe http://www.devoesquared.com PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Re: DO compatibility with Apple DO
Fair enough, sorry for asking a Q already answered there.I wonder if the change to OS X 86 + their XML format for archiving holds any new hope for compatibility... does it? I suppose not.On Nov 26, 2005, at 8:10 PM, Fred Kiefer wrote:Jiva DeVoe wrote: What're the technical barriers that prevent GS DO from being compatiblewith Apple DO?What's the chances of those being overcome? I know this is not the most polite answer, but this question is on ourFAQ. As I needed some time to find the Developer FAQ on our web sitemyself, I will share the answer with you:1.1.4 Can I transfer archived data from GNUstep to Cocoa? Apple's archiving format is proprietary and not documented, so thisposes a problem for anyone wanting to implement compatibility with it.However, even if we reverse engineered the format, there are enoughdifferences between the class and ivar layouts to make this sort ofcompatibility difficult. Not to mention the fact that we wouldconstantly have to keep up with the changes Apple made. Also Apple'sarchiving format, as far as we know, would not be compatible betweendifferent machines because of endiness issues, although GNUstep doesn'thave this problem. Your best bet is to implement your own archiving format that would workboth with GNUstep and Cocoa. Fortunately, you don't have to start fromscratch, since this has been essentially done for you in the nib2gmodeltool, which has an archiver that works both on GNUstep and Cocoa. Itmight be nice to split this off into a separate project to make iteasier for other people to do the same thing. 1.1.5 Does distributed objects work between GNUstep and Cocoa? See the answer to the previous question (on archive compatibility) forwhy this won't work either. -- Jiva DeVoe http://www.devoesquared.com PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
Notification once a minute - for a clock...
So I'm sorta hacking on WildMenus this weekend, and have implemented a primitive clock in the menubar... I'm wondering what's the best way to get my clock to redraw once a minute? Obviously the menu code itself gets linked into each application, so having 20 applications all launching their own little background timers to update the menubar clock sounds kinda cruddy. What would be the best way to do this? I imagine some kind of NSNotification but that also seems cruddy.(ps: For those who want said functionality - I have been sending patches to Michael Hanni, the WildMenus maintainer, so look for a release from him eventually.) -- Jiva DeVoe http://www.devoesquared.com PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
DO compatibility with Apple DO
What're the technical barriers that prevent GS DO from being compatible with Apple DO?What's the chances of those being overcome? -- Jiva DeVoe http://www.devoesquared.com PowerCard - Intuitive Project Management for Mac OS X ___ Gnustep-dev mailing list Gnustep-dev@gnu.org http://lists.gnu.org/mailman/listinfo/gnustep-dev
