e URL to on the bash command line to cmake.
Thanks for the quick feedback!
Cheers,
--
Szilárd
On Mon, Apr 9, 2018 at 5:44 PM, Haocheng Liu wrote:
> Hi Szilard,
>
> I tried it in CMake 3.10 and it works fine(No slash is dropped). Which
> version of CMake are you using?
>
> On Mon,
Hi,
I'm trying to pass a URL (that's used in ExternalProject_Add), and I'm
having trouble convincing bash + cmake to cooperate. No matter what
I've done, one fo the "/" gets dropped from "http://";.
Any ideas how can I construct an invocation similar to the one below
that will actually work?
cma
newlines but build without
problem on Windows (msvc, intel, gcc). Why does CMake need two
separate packages with different newlines?
Cheers,
--
Szilárd
On Fri, Jan 10, 2014 at 2:56 PM, Andreas Pakulat wrote:
> Hi,
>
> On Fri, Jan 10, 2014 at 2:16 PM, Szilárd Páll wrote:
>>
>&g
Found a workaround:
$ find /tmp/cmake-2.8.12.1 -type f | xargs dos2unix
This must be a bug, should I file a report?
--
Szilárd
On Fri, Jan 10, 2014 at 1:21 PM, Szilárd Páll wrote:
> Hi,
>
> I'm trying to compile 2.8.12.1, but I keep bumping into an error:
> [...]
>
Hi,
I'm trying to compile 2.8.12.1, but I keep bumping into an error:
[...]
/tmp/cmake-2.8.12.1/Bootstrap.cmk/cmConfigure.h:27:24: warning:
missing terminating " character [enabled by default]
"8define CMAKE_DATA_DIR "/share/cmake-2
[...]
This seems to be caused by a rather messed up-looking cmCo
On Sat, Jan 14, 2012 at 6:18 PM, Szilárd Páll wrote:
> Hi,
>
> It looks like there is a typo in FindOpenMP.cmake, on Windows the
> appropriate Intel Compiler flag is "/Qopenmp" not "-Qopenmp" (see
> http://goo.gl/NPbiJ).
>
> Before filing the bug could
Hi,
It looks like there is a typo in FindOpenMP.cmake, on Windows the
appropriate Intel Compiler flag is "/Qopenmp" not "-Qopenmp" (see
http://goo.gl/NPbiJ).
Before filing the bug could somebody test/confirm this -- I can't
exclude the possibility that the compiler silently accepts "-Qopenmp",
bu
On Fri, Jan 13, 2012 at 6:23 PM, Sean McBride wrote:
> On Fri, 13 Jan 2012 17:54:23 +0100, Szilárd Páll said:
>
>>Additionally, IMHO it's quite unfortunate that such a widely used
>>compiler as the Intel Compiler has such flaky support in CMake.
>
> Searching today
Hi,
I'm using the Intel Compiler v12 and to have a robust build generator,
before adding flags to CFLAGS I test them.
The following buggy behavior exists in CMake up to v2.8.7:
- As Intel issues
"icc: command line warning #10006: ignoring unknown option '-asdf'"
type warnings which are not handl
I would also very much like to see some form of grouping to be
possible in ccmake. Right now, the only way to avoid clutter is to
mark the large majority of the variables as advanced and keep only the
ones that would be used frequently used and this is still just a
half-baked solution.
One neat wa
Thanks Rolf & Michael for the explanation and tips, now it's clear
what the colons are for! I will see if CMAKE_NO_BUILTIN_CHRPATH is
feasible in our project or not.
Regard,
--
Szilárd
On Thu, Jun 9, 2011 at 11:48 PM, Michael Hertling wrote:
> On 06/09/2011 01:08 PM, Rolf Eike Beer wrote:
>>>
Hi,
I see strange rpath in binaries inside the build tree, linked in such
a way that these can run from the build tree. In some cases the rpath
list contains a fairly large amount of ":"-s, sometimes only one at
the end. Already one colon is unnecessary (at least in my case), but
the case when the
Hi,
I need to do some funky things to get my code compiled and I'd like to
have some opinion on whether these things are possible or not and
what's the best way to do it.
1. Change the C/C++ compiler from CMakeList.txt without triggering the
re-generation of the entire cache. I know it sounds st
ghtforward to
implement this feature for at least a dozen *NIX OS-es. In particular,
I like the suggestion that Philip Lowman suggested
(http://www.mail-archive.com/cmake@cmake.org/msg21354.html).
--
Szilárd
On Wed, Nov 3, 2010 at 5:57 PM, Michael Hertling wrote:
> On 11/02/2010 10:54 PM,
Hi,
In order to be able to run binaries linked dynamically to some
libraries from the same project the rpath in the build directory has
to point to the lib directory in the build directory. However, this
brakes CPack which seems to require the
CMAKE_BUILD_WITH_INSTALL_RPATH set on to work flawless
Hi,
I've been trying to implement a feature which would enable building
static binaries with cmake, but I've got completely stuck, I hope
someone can hint me what's the best way to do this.
What I've done is a 2 stage solution for making static binaries:
1) Telling cmake to prefer picking up ".a
> No black magic, just cmake's rules about variable contents.
> Basically CMake has only 1 type of variable value, thats a string. What
> you created above is a string variable "DEPS" with the value "dep1 dep2
> dep3", i.e. a single string consisting of 3 words separated by spaces.
> Some strings a
manually listing the latter instead of using the DEPS variable
works as well as adding them one-by-one in a loop (where also a
variables is used).
This seems to be _extremely_counterintuitive! Is there some sort of
CMake black-magic or basic rule that I don't know of?
--
Szilárd
On Sun, Sep 26,
> The DEPENDS option of ADD_CUSTOM_TARGET() is meant for file-level
> dependencies only; use ADD_DEPENDENCIES() for target-level ones.
Silly mistake, thanks for pointing it out. However, even if I add
target dependencies using ADD_DEPENDENCIES() it seems to take into
account only the dependent the
Hi,
I implemented a custom target which depends on several other targets,
including some that I generate beforehand as custom targets and
collect their names in a variable. However, this seems to behave in a
strange way if I list these dependencies like this:
add_custom_target(foo COMMAND [...]
20 matches
Mail list logo
