On Fri, Sep 13, 2013 at 6:23 AM, xantares 09 <xantares09@xxxxxxxxxxx> wrote:
>
>
> ________________________________
> Date: Thu, 12 Sep 2013 21:48:26 -0400
> Subject: Nested cmake?
> From: chmorgan@xxxxxxxxx
> To: libftdi@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> Hello.
>
> I was looking at how to use libftdi in the context of a project I'm working
> on without having to install it to a system directory. The project already
> uses cmake and I noticed libftdi does as well.
>
> I was thinking I could just add add_subdirectory() with the libftdi
> directory and then retrieve the output library paths from the top level and
> set global properties so some applications could set their include and
> libraries to use the libraries that were built. Is anyone else doing this?
>
> I added the libftdi directory to my project and did discover some issues
> with including the libftdi in the main cmakelists.txt file, specifically
> that the libftdi cmake file uses CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR and
> this is looking for and outputting files relative to the main cmake file.
>
> Would it be reasonable to make the libftdi cmake files operate relative to
> their location? I've made changes locally and everything appears to work
> correctly in both the normal case of running using the libftdi cmake as the
> base file and in my case of nesting it within my larger cmake build setup.
>
> I'll send a patch tomorrow so it's clear what I mean. I was hoping someone
> had some advice on the idea of using the library without installing it.
>
> Chris
>
>
> ________________________________
> libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
> To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
>
>
> Hello,
>
> You're doing it wrong, you can use find_package:
>
> 0. look at the cmake example in example /examples/cmake_example/.
>
> 1. Install libftdi where you want by passing
> CMAKE_INSTALL_PREFIX=/home/bob/mylibfti/install to cmake configuration, this
> should install
> /home/bob/mylibftdi/install/lib/cmake/libftdi1/LibFTDI1Config.cmake
>
In my case the project is kept in version control and I was hoping to
keep everything inside of the build directory when building.
I also have a series of chained CMakeLists.txt files, one at the root,
one in libraries/ and then /libraries/libftdi1-1.0/CMakeLists.txt.
We also do out-of-source builds in a parallel directory fyi.
With the current cmake scripts in libftdi1-1.0 I'd end up writing a
shell script that would be called by /libraries/CMakeLists.txt that
would go to the output, out-of-source directory, run cmake on the
libftdi1-1.0 directory, and then I'd have to figure out where in my
parallel build output to install it....
I'm not opposed to it, I'm just not sure how to do this in the most sane manner.
> 2. Use find_package(LibFTDI1) in your project, and pass
> -DLibFTDI1Config_DIR=/home/bob/mylibfti/install/lib/cmake/libftdi1 to your
> cmake configuration (only needed for non-system libftdi installations).
>
> 3. Link with LIBFTDI_LIBRARIES in your project, done.
>
> x.
>
>
>
> ________________________________
>
> libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
> To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
>
>
--
libftdi - see http://www.intra2net.com/en/developer/libftdi for details.
To unsubscribe send a mail to libftdi+unsubscribe@xxxxxxxxxxxxxxxxxxxxxxx
|
