How can I wrap cache variables from CMake scripts? Let's say I have a CMake
project, it depends on any third part library (says SFML or SDL), that
project expose a plenty of CACHE variables so that configuring them for
each build manually is a pain.
How can I configure from MY project THOSE
20150109)
+set(CMake_VERSION_PATCH 20150110)
#set(CMake_VERSION_RC 1)
---
Summary of changes:
Source/CMakeVersion.cmake |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
hooks/post-receive
--
CMake
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 2cfa421ac245f83e98783ecb677bbe69def1e1e0 (commit)
via
I tried that but then target_link_libraries will automatically add “-l” in
front of every additional flag I pass. Is there a way to pass other flags
without having it changed them?
i.e.:
target_link_libraries(${PROJECT_NAME} -Wl,--start-group foo bar -Wl,--end-group)
…ends up like this in the
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 76e41f6262ebabcc7e60ecd8112e09fa928e07db (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 8b355d64de0d1d899a0c58a12285b7514f8d8e18 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via cf0d9e84916ebbcd14fd3df5fd8b9b856c1edb5b (commit)
via
On 29 December 2014 at 19:02, Evangelos Foutras evange...@foutrelis.com wrote:
Since commit 854e762 (FindRuby: clean up querying variables from Ruby)
we query RbConfig::CONFIG first and, if the command fails or its output
equates to a false constant, then fall back to querying Config::CONFIG.
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via a9adf6ad4b1300a805dca29fe8e09d4db3c9fd73 (commit)
via
I updated my CMakeLists.txt to create an NSIS installer under a Nmake
Makefile.
The packaging works without errors when run with 'nmake package'.
However, the resulting exe file when run, returns:
Bad file number.
The problem happens on both builds for win32 and win64.
The NSIS installer is
On 2014-10-03 03:35, Rolf Eike Beer wrote:
find_package(foo 2.0 EXACT) means EXACT, i.e. only 2.0 is allowed. In most
cases this behavior is not the one that one would expect or need. Most people
would instead allow any 2.0.x version to match. This sort of selection is
currently impossible
Matthew Woehlke wrote:
On 2014-10-03 03:35, Rolf Eike Beer wrote:
find_package(foo 2.0 EXACT) means EXACT, i.e. only 2.0 is allowed. In
most cases this behavior is not the one that one would expect or need.
Most people would instead allow any 2.0.x version to match. This sort of
selection
Indeed I have tried several ways to create and build projects without
using CMake at all, and so far no luck--I still get requires
elevation errors. I don't have a solution for my problem yet but it
appears that whatever it is that is stopping me from building projects,
CMake does not cause
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via b5061d40e11d93a449736ffa0b363a36bea97898 (commit)
via
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via 5f3322884cc5903d3198f760191e2990c361330d (commit)
via
On 08/01/15 21:56, J Decker wrote:
I don't think you should install libraries like that... things in
binary would be build products, can you possibly just install the libs
as normal
INSTALL( Target ... LIBRARY DESTINATION lib )
The lib files are not built by cmake but are dependencies for my
need to use install( PROGRAMS ... ) then
On Fri, Jan 9, 2015 at 7:52 AM, Gonzalo Garramuno ggarr...@gmail.com
wrote:
On 08/01/15 21:56, J Decker wrote:
I don't think you should install libraries like that... things in binary
would be build products, can you possibly just install the libs
On Fri, Jan 09, 2015 at 20:18:25 +0100, Rolf Eike Beer wrote:
Matthew Woehlke wrote:
On 2014-10-03 03:35, Rolf Eike Beer wrote:
find_package(foo 2.0 EXACT) means EXACT, i.e. only 2.0 is allowed. In
most cases this behavior is not the one that one would expect or need.
Most people would
The lib files are not built by cmake but are dependencies for my program.
You could move external libraries wih something like this:
install(FILES /some/location/libsomething.so DESTINATION lib)
The lib files are symbolic links to the /usr/local/lib directory. For
example:
Hi,
on Linux, libraries don't need the executable permission set.
HS
Am 9. Januar 2015 21:30:54 MEZ, schrieb J Decker d3c...@gmail.com:
need to use install( PROGRAMS ... ) then
On Fri, Jan 9, 2015 at 7:52 AM, Gonzalo Garramuno ggarr...@gmail.com
wrote:
On 08/01/15 21:56, J Decker wrote:
On 09/01/2015 05:55 p.m., J Decker wrote:
the symlinks already exist in the source directory (it sounds like)
the problem is they're not being packaged/extracted right...
Correct. I changed my symlink script with one that copies the libraries
and all problems are gone.
Now I am tackling
On 1/9/2015 12:43 PM, Gonzalo Garramuño wrote:
I updated my CMakeLists.txt to create an NSIS installer under a Nmake
Makefile.
The packaging works without errors when run with 'nmake package'.
However, the resulting exe file when run, returns:
Bad file number.
The problem happens on both
I realize the cmake documentation says that everything that starts with “-“
should be treated as other linker flags, so I wonder, perhaps it’s a new bug,
or maybe just with a specific generator? In this case I am using the new NVidia
NSight Android generator for Visual Studio.
Can anyone
install( PROGRAM ) will keep executable permissions... (as opposed to
using FILES or DIRECTORY ) not sure about symlinks
Hm forgot about this one... Had problems with it years ago on AIX and
stopped using it back then (it removed baked in paths to libraries
from executables)... Time
On Fri, Jan 9, 2015 at 12:54 PM, Domen Vrankar domen.vran...@gmail.com
wrote:
install( PROGRAM ) will keep executable permissions... (as opposed
to
using FILES or DIRECTORY ) not sure about symlinks
Hm forgot about this one... Had problems with it years ago on AIX and
stopped
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project CMake.
The branch, next has been updated
via e51cf4204b190f9e85186b3552634bb7bc22f76d (commit)
via
Hi,
Have a look here: http://www.cmake.org/Bug/view.php?id=15291
You should be able to use, for the time being, DOWNLOAD_COMMAND and
UPDATE_COMMAND to achieve this. (have not tested myself)
Hope this helps.
Cheers,
Yngve
On 08/01/15 23:58, Kent Williams wrote:
I'm building the Mozilla
27 matches
Mail list logo
