Hi,
On Mon, Mar 7, 2016 at 9:29 PM, Ivan wrote:
> Hello!
>
> Here is my CMakeLists.txt:
>
> cmake_minimum_required(VERSION 3.3)
> project(untitled19)
>
> set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++11")
>
> set(LIBRARY_SRC library.cpp)
>
> add_library(libra SHARED ${LIBRARY_SRC})
>
> set(SOU
Hi, I am new to cmake and really hope am doing this correctly. I asked
stackoverflow but didn't get a good enough answer for my specific problem
here;
If I want root/sub-directories/ as separate sub-projects that can be
compiled using the individualCMakeLists.txts in their folders I find myself
li
On 3/7/16, Eric Wing wrote:
> On 3/7/16, David Cole wrote:
>> If you include those files in the source list for a library, executable,
>> or
>> custom target, they should show up in IDE projects, and they should be
>> ignored by Makefile type projects. Have you tried that?
>>
>>
>> David
>>
>
> I
On 3/7/16, David Cole wrote:
> If you include those files in the source list for a library, executable, or
> custom target, they should show up in IDE projects, and they should be
> ignored by Makefile type projects. Have you tried that?
>
>
> David
>
I haven't tried it yet since I was wondering
If you include those files in the source list for a library, executable, or
custom target, they should show up in IDE projects, and they should be ignored
by Makefile type projects. Have you tried that?
David
> On Mar 7, 2016, at 6:34 PM, Eric Wing wrote:
>
> I have a bunch of .cmake support
I have a bunch of .cmake support files in my project that I have split
off from CMakeLists.txt (using INCLUDE to combine them) to separate
concerns. (Source files, application assets, script files, platform
settings, codesigning, etc.)
This works, but they don't show up in IDEs (Visual Studio, Xco
Hi all,
Is there any update on this issue?
I believe this addition would be really useful.
Best regards,
Xavier
On Sat, Nov 29, 2014 at 4:12 AM, Rob Zumwalt wrote:
> Apologies for the new thread, I just subscribed in order to comment on
> this, and didnt know how to reply in the existing th
Hi Srinath,
I guess you will find what you need here:
https://cmake.org/Wiki/CMake_RPATH_handling
Best regards,
Xavier
On Mon, Mar 7, 2016 at 4:35 PM, Srinath Vadlamani <
srinath.vadlam...@gmail.com> wrote:
> Hello All,
> How do I keep the rpath used during the build of an executable the sa
Hello!
I hope someone could finally help me. I spent about two days to find solution
for my problem, but with no luck.
Here is my problem:
I want to create a shared library (dll on Windows, .so on Linux, .dylib on OS
X) that contains some functions. This library should export only these
functi
Hello All,
How do I keep the rpath used during the build of an executable the same
when I install that executable using INSTALL(TARGETS )?
I do set :
SET(CMAKE_INSTALL_RPATH_USE_LINK_PATH TRUE)
=
Srinath Vadlamani
=
--
Power
Dear CMakers,
I encountered a strange problem with my cmake setup:
In my CMakeLists.txt files there is a line
install(TARGETS ${PROJECT_NAME} DESTINATION ${CMAKE_BINARY_DIR})
Some of my projects use add_subdirectory, and with make install I "pull" them
right to the build directory.
This used to
Short version: no.
Long version: Visual Studio is heavily built around MSBuild as the back-end of
execution of various tasks. While theoretically it could be done that MSBuild
only acts as a relay and calls into Ninja scripts, you would lose the entire
feature set of Solution Explorer, which is
12 matches
Mail list logo
