On Wed, Sep 10, 2014 at 4:52 AM, Stephen Kelly <[email protected]> wrote:

> Richard Shaw wrote:
>
> > Everyone has been really helpful but I don't want to be a pest.
> >
> > Is there a specific find package module that one could point to that
> would
> > be consider the gold standard of getting it right? One with sufficient
> > complexity (not like the wiki example).
>
> Have you looked at
>
>
> http://www.cmake.org/cmake/help/git-master/manual/cmake-developer.7.html#a-sample-find-module
>
> too?


Thanks, that has a little more detail, but the module I'm trying to clean
up is this one:

http://www.cmake.org/gitweb?p=cmake.git;a=blob;f=Modules/FindFLTK.cmake;hb=HEAD

It does a lot of questionable things, I think much of it due to the fact
it's been unmaintained for so long and some of the newer commands were
probably not available when it was written.

One wrinkle is that you can't trust the 'fltk-config' program. If you
specify "--libs" it will give you the static library location even if only
shared libraries were built, so it only uses that to get the library
location, not the library itself.

The actual reason I took over the module is that it doesn't add the correct
flags (--ldstaticflags) if you ARE actually using static libraries, but
after some investigation, it really need a lot of cleanup/modernization
work and I'm not sure I'm completely qualified to be the one to do it :)

Thanks,
Richard
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Reply via email to