On 7/27/22 23:07 Daniel Silva wrote:
> I want more control of the compilation process, linking the fltk
> relative to my project folder, without having the install, because I
> want to stay up to date with the project and linking it staticly.
> But it's pretty hard to get the necessery fltk dependecies to compile
> my application within my Makefile.
> The fltk-config --ldflags doesn't return all necessery libs
> dependecies, but I noted the first definition of LDLIBS var inside the
> fltk-config has the dependecies, but I can't get it in a nicer way
> other than copy manually.
> So my setup is a mess,  so I'm doing this completly wrong?

Greg wrote a long answer that should cover what you need. Please read
this as well.

The short answer to your question *might* be that you should use
`fltk-config --ldstaticflags` rather than `fltk-config --ldflags`if you
want static linking.

If you look at Greg's recipe he's using ldstaticflags as well.

> https://github.com/daninsky1/inkbreaker
>
> In the make folder I got the NMake Makefile.vc for windows and make
> Makefile for linux.

I'm not sure how this would apply to NMake Makefiles though but hope it
helps.

--
You received this message because you are subscribed to a topic in the Google Groups "fltk.general" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/fltkgeneral/vj6Z_3KufEw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to fltkgeneral+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkgeneral/01c0f6b5-3526-9076-b3a2-f0d0c6c58990%40online.de.