[CMake] CMake binary output directory for Visual Studio project with generated MinGW fortran projects
J Decker
d3ck0r at gmail.com
Thu Oct 30 00:59:58 EDT 2014
when I asked a similar question years ago, someone said to make install
rules so everything would be copied together; works for combinations of
tools; works consistently for all generators then. Install directory is
relative to the build directory if not an absolute path.
Have to set debug properties of visual studio project before running
instead of just immediately running; but once it's set you can just build
install and immediately run.
On Wed, Oct 29, 2014 at 2:35 PM, Neal Kruis <
neal.kruis at bigladdersoftware.com> wrote:
> CMakers,
>
> I'm wondering if any of you can help me with a question that I've posted
> to Stack Overflow:
>
>
> http://stackoverflow.com/questions/26637673/how-to-set-the-cmake-binary-output-directory-for-visual-studio-project-with-gene
>
> Essentially, I'm finding that the cmake_add_fortran_subdirectory function,
> which uses MinGW, doesn't produce binaries in the same directory as the
> master Visual Studio project. My question is about getting all of the
> binaries created in the configuration directory (e.g., Debug, Release,
> etc.).
>
> Any ideas would be appreciated!
>
> --
>
> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/cmake/attachments/20141029/544fed2b/attachment-0001.html>
More information about the CMake
mailing list