Dear all,
I'm quite new in CMAKE. The compilation of our sources (EUROPLEXUS) under
Windows is running very well but under Linux I get an error while cmake is
copying the module files. For one particular file, cmake uses a wrong filename.
See the two bold lines below.
Any idea?
Many thanks
Marti
Thanks Craig, I hadn't found that article yet
On Wed, Aug 23, 2017 at 4:37 PM, Craig Scott
wrote:
>
>
> On Thu, Aug 24, 2017 at 5:20 AM, Jom O'Fisher
> wrote:
>
>> We'll definitely be discussing this use case at our next C++ meeting and
>> I'll also be checking for myself whether ccache will wo
On Thu, Aug 24, 2017 at 5:20 AM, Jom O'Fisher wrote:
> We'll definitely be discussing this use case at our next C++ meeting and
> I'll also be checking for myself whether ccache will work in this CMake
> scenario. If ccache does work it seems like the natural level at which to
> fold identical bu
Ok got it sorry to hear that certainly because, as soon as I hear something
that would be useful somehow I end up needing it the next day. So sorry
for us both.
>From what your are saying (and I will take your word for it) the CMake has
a another problem in not implementing "inherited build prope
> Does that work for your needs?
Sadly, no (but thanks!). While this is enough for the arguably common use
case of include directories, compile flags, etc... there are plenty of
things that won't work with this approach.
e.g. none of this works for instance:
project(foo)
add_library(blah INTERF
So there is some odd replies in the cmake mailing list possibly
responses to wrong message, but this looked like a response to mine
even if the initial reply to bit is not right from Nicholas. Anywho
here goes:
@Jean-Michaël Celerier
-- snip --
>* - Says that custom functions such as add_{projec
By gradle module projects, I just mean the leaf build.gradle files as
opposed to the root build.gradle. By configurations, I mean Build Types
(debug vs release) and Product Flavors (demo vs free vs paid). Hereafter I
will use the term "variant" rather than "configuration" to be precise. See
this wr
On Wed, Aug 23, 2017 at 2:07 AM, Clément Gregoire wrote:
> I can't argue too much why paths or absolute on cmake as I don't know the
> rationale behind it is. While your point about command line limit makes
> sense, I feel like a system limiting command line size to this extent is
> dumb if it do
On 23.08.2017 22:21, Andrew Bell wrote:
Hi,
Can someone please explain the cmake regex matching rules?
The following returns true:
if ("This is a test" MATCHES "test")
I would have expected to have needed something like this to get a match:
if ("This is a test" MATCHES ".*test")
Does cmake
Hi,
Can someone please explain the cmake regex matching rules?
The following returns true:
if ("This is a test" MATCHES "test")
I would have expected to have needed something like this to get a match:
if ("This is a test" MATCHES ".*test")
Does cmake always search for a subexpression? Is the
I'm not sure what you mean by "gradle module projects", but maybe
having some examples of what you mean by "configurations, C++ flags,
etc" might make it more clear.
Question: When specifying "path" for the CMakeLists.txt in the
build.gradle file, how do you know which targets to build? For
exampl
A quick scan of CMake source code shows that we don't have any
references to gcc_eh anywhere. I way this could be occurring is
through CMake detection of the implicit libraries that a compiler
requires for each language. In particular it could be that C code for
mingw by default uses gcc_eh while C
Thanks for the write-up Robert. Having thought about it, I don't believe we
have a satisfying answer at the gradle level for this kind of organization.
In the gradle model module projects are the unit of organization for
configurations, C/C++ flags, etc. and that's something we're pretty much
stuck
2017-08-23 15:28 GMT+02:00 Clément Gregoire :
> set_property(GROUP PluginGroup PROPERTIES /* whatever in
>> cmake-properties*/)
>>
>> set_group(myTarget PluginGroup) // applies everything to the target
>
>
> Isn't it the same as having a custom target/library for the group and
> linking it
On 08/23/2017 05:07 AM, masaru tsuchiyama wrote:
> It seems your coworker can reproduce it and you can use the PC tomorrow.
> So I don't need to debug it, right?
Correct, thanks. See issue for further updates.
-Brad
--
Powered by www.kitware.com
Please keep messages on-topic and check the CM
2017-08-23 14:10 GMT+02:00 Jean-Michaël Celerier <
jeanmichael.celer...@gmail.com>:
> > - Says that custom functions such as add_{project}_library shouldn't be
> used and function definitions should be used as little as possible. Except
> this just leads to extremely verbose CMakeLists where repea
> - Says that custom functions such as add_{project}_library shouldn't be
used and function definitions should be used as little as possible. Except
this just leads to extremely verbose CMakeLists where repeated properties
are defined again and again and again.
I also never understood how to handl
On 23.08.2017 11:44, Nicholas Devenish wrote:
> - But simultaneously advocates rewriting internal functions using the
> (undocumented?) '_' feature to access "previous definitions". Uses this
> as one of the few examples of one of the steps as a method to allow a
> script to change behaviour if bei
On Wed, Aug 23, 2017 at 8:07 AM, Clément Gregoire wrote:
> I entirely agree with for the rest. CMake badly documenting good practices
> or even giving tutorials is an issue. Probably the biggest issue I found. I
> myself still fight after years of using and experimenting with it. This
> lead to a
Hello
It seems your coworker can reproduce it and you can use the PC tomorrow. So
I don't need to debug it, right?
Ifyou want me to do anything, le me know.
Regards
Masaru
2017年8月23日(水) 7:34 masaru tsuchiyama :
> Hello
>
> I'm busy today.
> So I'll try tomorrow or the day after tomorrow.
>
>
Greetings.
I'm a developer on a fairly large project where I'm using CMake version
3.9.1
I primarily work on linux, but also cross compiles for windows using
Mingw-w64 on my linux box.
I have encountered an issue which I'm having some trouble figuring out.
Running through some of my tests where
I can't argue too much why paths or absolute on cmake as I don't know the
rationale behind it is. While your point about command line limit makes
sense, I feel like a system limiting command line size to this extent is
dumb if it doesn't allow reading more arguments through a file. (again, I
don't
22 matches
Mail list logo
