Re: GNUstep-make and C++ projects...

2008-03-01 Thread Jiva DeVoe 

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...

2008-03-01 Thread Helge Hess 

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...

2008-03-01 Thread Nicola Pero 
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...

2008-03-01 Thread Jiva DeVoe 
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...

2008-03-01 Thread Jiva DeVoe 

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...

2008-03-01 Thread Helge Hess 

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

Next release

2008-03-01 Thread Adam Fedor 
It's time for another release.  I'll make an unstable release of the  
core libraries late next week.   I also plan a stable base release,  
but I will not make a stable release of the gui libraries, unless  
there is some important patch the someone wants there (or better yet,  
patch the stable branch yourself so I don't have to do it).


Let me know if there is some reason I should wait.


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: gnustep on windows

2008-03-01 Thread Xavier Glattard 
Fred Kiefer  gmx.de> writes:

> This looks rather nice and it shows that I was wrong, there is a bit
> more X specific code inside of CairoContext. Did you get this code to
> work? I remember that there was also some complicated extension needed
> for the configure script, wasn't it?
> 
> And you did forget to add the header files 
> 
> Cheers,
> Fred

You're so right :-)
The fixed zip file is online. It has to be unzipped in the back (or back/trunk)
directory.

No need for a special configure script : the current one is fine.
I pushed the 'complicated extensions' in the repository a long time ago.
Just in case :-)

This code partialy worked : i can remember some smooth text in a menu.
Cairo on glitz did not work.

You made many changes in the cairo backend : i can get my code work now. But it
is build.

Regards

Xavier








___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUstep-make and C++ projects...

2008-03-01 Thread Nicola Pero 
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...

2008-03-01 Thread Tim McIntosh 

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...

2008-03-01 Thread Jiva DeVoe 

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 on windows

2008-03-01 Thread Fred Kiefer 
Paul Fox wrote:
>> Out of curiosity, why do you want to use cairo on Windows and not the
>> native window interface (or one based on GDI+)?
> 
> Why Cairo? Mainly because it gives me a fairly nice graphics library
> that's cross-platform. For fancy graphics, Cairo gives a consistent
> appearance across platforms, allows me to ignore platform when coding
> for the most part, and is much nicer looking than GDI. I'm really still
> exploring what's possible here, and it appears that Cairo is the most
> potentially capable backend.

When programming with GNUstep you will be working against the GNUstep
drawing API, not cairo or GDI. It is true that the implementation of
this API for cairo is more complete, but even that may be changed.


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: gnustep on windows

2008-03-01 Thread TMC 


Paul Fox wrote:
> 
> On a side note, I've heard that there are plans for a theming API, but 
> I've had some difficulty finding any details. Where could I find out 
> about that?
> 
You might be talking about [Camaelon][1] (spelling is important).

[1]: http://www.etoile-project.org/etoile/mediawiki/index.php?title=Camaelon

--Tycho Martin Clendenny
-- 
View this message in context: 
http://www.nabble.com/gnustep-on-windows-tp15760118p15769005.html
Sent from the GNUstep - Dev mailing list archive at Nabble.com.



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: gnustep on windows

2008-03-01 Thread Paul Fox 

There shouldn't be any X dependencies in the cairo backend code apart
from the X surfaces of course. You should be able to provide your own MS
Windows surface and use that. This gets a bit harder on the make file
level, here our config scripts currently only support the cairo backend
for X11.
There is one other problem I see, although freetype is available for
Windows you will most likely want to use native font support. For this
you will need to implement your own classes or port the ones from the
the winlib backend.
Out of curiosity, why do you want to use cairo on Windows and not the
native window interface (or one based on GDI+)?


Why Cairo? Mainly because it gives me a fairly nice graphics library that's 
cross-platform. For fancy graphics, Cairo gives a consistent appearance across 
platforms, allows me to ignore platform when coding for the most part, and is 
much nicer looking than GDI. I'm really still exploring what's possible here, 
and it appears that Cairo is the most potentially capable backend.

Yeah, the config scripts will be a bother if I do this, especially given that I have very little knowledge or experience with sh scripting or the GNU Build System (such experience as I have makes me want a better build system.) 


There already is some limited theming available in GNUstep. You find the
API and the code for it in gui/Source/GSTheme.m.


Thanks, I'll take a look.

Paul



___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

Re: GNUstep-make and C++ projects...

2008-03-01 Thread Helge Hess 

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 on windows

2008-03-01 Thread Fred Kiefer 
Xavier Glattard wrote:
> Hello
> 
> Some months (a year ?) ago i tried to write a Cairo backend for windows.
> You can get the files there :
> http://amstradstuff.free.fr/GNUstep/back-win32cairo.zip
> Put then in Source/cairo directory
> 
> Achtung : two files will be overwritten !!
> 
> I'm not sure they still can be build as cairo backend has been changed 
> but they may be a first step.
> You will need FreeType and fontconfig.
> 

This looks rather nice and it shows that I was wrong, there is a bit
more X specific code inside of CairoContext. Did you get this code to
work? I remember that there was also some complicated extension needed
for the configure script, wasn't it?

And you did forget to add the header files :-)

Cheers,
Fred


___
Gnustep-dev mailing list
Gnustep-dev@gnu.org
http://lists.gnu.org/mailman/listinfo/gnustep-dev

RE: GNUstep-make and C++ projects...

2008-03-01 Thread Nicola Pero 
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