Baptiste Derongs <> wrote:
> Actually I have a file that contains a lot of functions, call this
> file global.c.
> Next I have multiple files, call them f1.c, f2.c, ...
>
> And each f*.c has to be compiled with global.c.
Make a static library containing global.c, then link each application to
it.
On 10/4/07, Torsten Martinsen <[EMAIL PROTECTED]> wrote:
> Baptiste Derongs <> wrote:
>
> > The point is that I want a MakeFile that creates only the .o file,
> > doesnt try to get binary. Next that same Makefile (and other ones)
> > need the .o file to make other binaries.
>
> Instead of focussing
Baptiste Derongs <> wrote:
> The point is that I want a MakeFile that creates only the .o file,
> doesnt try to get binary. Next that same Makefile (and other ones)
> need the .o file to make other binaries.
Instead of focussing on how to do this small step, you should probably
explain what it is
> On Wednesday 03 October 2007 16:27:14 Baptiste Derongs wrote:
> > Hello all,
> >
> > I just begin in using Cmake (but I'm going faster than I never went
> > with any configure.in), and I am wondering how to get a '.o' file (how
> > to call gcc -c in fact).
> >
> > I tried to set CMAKE_C_FLAGS to
On Wednesday 03 October 2007 16:27:14 Baptiste Derongs wrote:
> Hello all,
>
> I just begin in using Cmake (but I'm going faster than I never went
> with any configure.in), and I am wondering how to get a '.o' file (how
> to call gcc -c in fact).
>
> I tried to set CMAKE_C_FLAGS to "-c", it kind of
Hello all,
I just begin in using Cmake (but I'm going faster than I never went
with any configure.in), and I am wondering how to get a '.o' file (how
to call gcc -c in fact).
I tried to set CMAKE_C_FLAGS to "-c", it kind of worked, but it doest
seem very generic
Is there any better solution ?
R
