[CMake] object file target

2007-07-30 Thread Juan Sanchez
Is there a command for creating a .o target on Linux? If I create my own custom command for creating an object, the .o file is being recompiled every time. I need the dependency scanner to recognize when a .cc file does not need to be compiled into a .o file. This is what I have right now.

Re: [CMake] object file target

2007-07-30 Thread Alexander Neundorf
On Monday 30 July 2007 16:24, Juan Sanchez wrote: Is there a command for creating a .o target on Linux? If I create my own custom command for creating an object, the .o file is being recompiled every time. I need the dependency scanner to recognize when a .cc file does not need to be

Re: [CMake] object file target

2007-07-30 Thread Juan Sanchez
It's pretty messy the Makefile I am trying to convert. It is trying to do something like this: g++ -shared obj1.o obj2.o obj3.o staticarchivex.a staticarchivey.a -o sharedlibrary.so The static archives are compiled with -fPIC so dynamic relocation is not a problem. Unfortunately, this only

Re: [CMake] object file target

2007-07-30 Thread Juan Sanchez
Did you try to make it straight-forward without any tweaking around?: add_library (staticarchivex STATIC ...) add_library (staticarchivey STATIC ...) add_library (sharedlibrary SHARED obj1.c obj2.c obj3.c) target_link_libraries(sharedlibrary staticarchivex staticarchivey) Any reason why

Re: [CMake] object file target

2007-07-30 Thread Andreas Pakulat
On 30.07.07 16:39:04, Juan Sanchez wrote: Did you try to make it straight-forward without any tweaking around?: add_library (staticarchivex STATIC ...) add_library (staticarchivey STATIC ...) add_library (sharedlibrary SHARED obj1.c obj2.c obj3.c) target_link_libraries(sharedlibrary

Re: [CMake] object file target

2007-07-30 Thread Hendrik Sattler
Am Montag 30 Juli 2007 23:39 schrieb Juan Sanchez: Did you try to make it straight-forward without any tweaking around?: add_library (staticarchivex STATIC ...) add_library (staticarchivey STATIC ...) add_library (sharedlibrary SHARED obj1.c obj2.c obj3.c)

Re: [CMake] object file target

2007-07-30 Thread Juan Sanchez
Thanks for the make VERBOSE=1. I was flying blind before that since it wasn't on the man page. That is great that the add_library it works, even when one of the static archives is external project. All I need to do now is figure our how to send --whole-archive to the linker for each of the

Re: [CMake] object file target

2007-07-30 Thread Brandon Van Every
On 7/30/07, Juan Sanchez [EMAIL PROTECTED] wrote: Thanks for the make VERBOSE=1. I was flying blind before that since it wasn't on the man page. It wasn't on the man page of your version of Make? Remember, CMake generates native build systems. You have to know your way around CMake, *and*

Re: [CMake] object file target

2007-07-30 Thread Hendrik Sattler
Am Dienstag 31 Juli 2007 00:16 schrieb Juan Sanchez: Thanks for the make VERBOSE=1. I was flying blind before that since it wasn't on the man page. That is great that the add_library it works, even when one of the static archives is external project. All I need to do now is figure our how

Re: [CMake] object file target

2007-07-30 Thread Juan Sanchez
Thanks everyone for their help. I'm evaluating cmake for my group and it appears that cmake meets many of the needs that we have. Regards, Juan Hendrik Sattler wrote: Am Dienstag 31 Juli 2007 00:16 schrieb Juan Sanchez: Thanks for the make VERBOSE=1. I was flying blind before that since it

Re: [CMake] object file target

2007-07-30 Thread Juan Sanchez
I didn't think to look on the make man page, since almost every gnu make system I dealt with had the verbose information by default. Doing a man make reveals nothing about VERBOSE=1 since that is specific to cmake, and doesn't have to do anything with the native build system. make VERBOSE=1

Re: [CMake] object file target

2007-07-30 Thread Brandon Van Every
On 7/30/07, Juan Sanchez [EMAIL PROTECTED] wrote: I didn't think to look on the make man page, since almost every gnu make system I dealt with had the verbose information by default. Doing a man make reveals nothing about VERBOSE=1 since that is specific to cmake, No I'm googling and it's

Re: [CMake] object file target

2007-07-30 Thread Bill Hoffman
Brandon Van Every wrote: On 7/30/07, Juan Sanchez [EMAIL PROTECTED] wrote: I didn't think to look on the make man page, since almost every gnu make system I dealt with had the verbose information by default. Doing a man make reveals nothing about VERBOSE=1 since that is specific to cmake,

Re: [CMake] object file target

2007-07-30 Thread Brandon Van Every
On 7/30/07, Bill Hoffman [EMAIL PROTECTED] wrote: Brandon Van Every wrote: On 7/30/07, Juan Sanchez [EMAIL PROTECTED] wrote: I didn't think to look on the make man page, since almost every gnu make system I dealt with had the verbose information by default. Doing a man make reveals

Re: [CMake] object file target

2007-07-30 Thread Juan E. Sanchez
Hi Brandon, By default, gnu make will always print the command to execute, as well as its output. Typically, the command to be executed is muted by prefixing an @. For example: @echo Built target PerlLib As for all of the other commands, apparently they used this trick: # Suppress