On 2019-01-21 11:09- Lars wrote:
Hello,
We are creating a foo-config.cmake file for a package. The 'foo' package contain a
dynamic library that provides two interfaces and a number of configuration files. There
is a mapping between an interface and required configuration files. What is
Alan,
Thank you very much for the response.
Our 'foo' package does not use CMake. That means there is no build-system to
produce the foo-config.cmake file, the file is manually created. The file does
allow different projects to import the target from 'foo' package that has been
installed.
Hi,
I have got some problems finding packages under windows platform.
I made a toolchain for VSCode and cmake 3.13 , but I don't understand
why it fails to find almost all of my packages dependencies
It is not able to find packages in the CMAKE_FIND_ROOT_PATH itself.
If I try setting
On Tue, 2018-12-18 at 08:22 +1100, Craig Scott wrote:
> If you are setting your own sysroot, are you using a toolchain file?
> You could put your set_property() command in your toolchain file if
> you're using one.
> Those techniques aside, it's interesting that you need to add this
> manual
good afternoon,
I am following the CMake book to learn about CMake. I have trouble to
follow chapter 3: build configurations
(https://riptutorial.com/cmake/example/26702/setting-a-release-debug-configuration)
In this part it is not very clear why these configurations are used,
and how they
Hi Lars:
On 2019-01-22 12:05- Lars wrote:
Alan,
Thank you very much for the response.
You are welcome.
Our 'foo' package does not use CMake. That means there is no build-system to
produce the foo-config.cmake file, the file is manually created. The file does
allow different
Dear Client,
Please find attached copy invoice as requested.
You can download view using this link
Regards
Julien Jomier
PH 346 844-3745
FAX 346 844-3837
e:julien.jom...@kitware.com
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ
Alan,
Appreciate you taking the time to help.
It is unfortunately not an option to move 'foo' package to CMake at this time.
To summarize, we want to perform find_package in config mode to a none-CMake
package that contain a target and some config files. Our current solution is to
manually
Hi Brad,
> Am 14.01.2019 um 12:44 schrieb Brad King :
>
> I've almost never needed to test the length of a list in CMake
> code. It's not very common in my experience. What is your
> customer trying to do?
Sorry for the late response! I’ve asked him. Mainly, he has three use cases:
-
On 1/22/19 3:08 AM, tors...@robitzki.de wrote:
> three use cases:
>
> - Checking for empty lists (I’ve showed him that this can be done
> by a string compare).
> - Checking for lists having more than 1 entry
> - Checking for equal size of two lists. For example, if you want
> to pass pairs or
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, master has been updated
via cb7fbf1dbbcc88fc7701250db5c3ccdf0ab7396e (commit)
via
On 1/22/19 7:09 AM, tors...@robitzki.de wrote:
>> Am 22.01.2019 um 12:42 schrieb Brad King:
>> Rather than a special `if` syntax, perhaps we could introduce an
>> explicit `$LIST_LENGTH{mylist}` syntax. One would need to experiment
>> to see if modifying the variable expansion parser (under
On 1/22/19 7:40 AM, Daniel Franke wrote:
> Whats about a Syntax like
>
> ${list::LENGTH}
That would require dispatch after matching `${VAR}` syntax, and
that lookup is one of the hottest paths according to profiling.
We already have $ENV{} and $CACHE{} syntax.
-Brad
--
Powered by
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, master has been updated
via bcc9ea2b3d9cd3b882dbb2a23502b0392cb21d1b (commit)
via
t a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 497feed..b06c382 100644
--- a/Source/CMakeVersion.cmake
+++ b/Source/CMakeVersion.cmake
@@ -1,5 +1,5 @@
# CMake version number components.
set(CMake_VERSION_MAJOR 3)
set(CMake_VERSION_MINOR 13)
-set(CMake_VERSION_PATCH 20190122)
+set(CMake_VER
I like some syntax that looks like $LEN{}.
I would love to keep the $...{ syntax open for future exentsion such
as easy target property set/get ( $[prop_name]{target} ) . This seems
to be okay as $ENV, and $CACHE only work on variables, so therefore
adding $LEN that also only works on variables
On 1/22/19 10:55 AM, Marc CHEVRIER wrote:
> What about introducing a syntax similar to the version comparison:
>
> * LENGTH_EQUAL
> * LENGTH_GREATER
> * LENGTH_LOWER
> * etc…
>
> To use it:
> if (my_list LENGTH_EQUAL 1)
> # do my stuff
> endif()
That's where this thread started.
On 1/22/19 1:31 PM, tors...@robitzki.de wrote:
> Currently, the Code that evaluates the ${}-Syntax only evaluates the key
>
> const char* cmCommandArgumentParserHelper::ExpandSpecialVariable(
That's the pre-CMP0053 impl.
See cmMakefile::ExpandVariablesInStringNew for the modern impl.
Only with
On Tue, Jan 22, 2019 at 19:31:43 +0100, tors...@robitzki.de wrote:
> Currently, the Code that evaluates the ${}-Syntax only evaluates the key, if
> the key is not an empty string:
>
> const char* cmCommandArgumentParserHelper::ExpandSpecialVariable(
> const char* key, const char* var)
> {
>
> Am 22.01.2019 um 16:37 schrieb Brad King :
>
> On 1/22/19 10:28 AM, tors...@robitzki.de wrote:
>> With `$CACHE{VAR}` and `$ENV{VAR}` we already have the syntax for calling a
>> „function“.
>
> No, there is no obvious way to pass arguments, handle nested quoting, etc.
Jep, you are right.
On 1/22/19 10:28 AM, tors...@robitzki.de wrote:
> With `$CACHE{VAR}` and `$ENV{VAR}` we already have the syntax for calling a
> „function“.
No, there is no obvious way to pass arguments, handle nested quoting, etc.
The language was not designed for that. That is a big can of worms I'd rather
I am not convince that the proposed syntax is a good idea because it introduce
a new syntax just to solve one action on a list.
What about introducing a syntax similar to the version comparison:
• LENGTH_EQUAL
• LENGTH_GREATER
• LENGTH_LOWER
• etc…
To use it:
if (my_list LENGTH_EQUAL 1)
# do
> Am 22.01.2019 um 13:33 schrieb Brad King :
>
> On 1/22/19 7:09 AM, tors...@robitzki.de wrote:
>
>> How about adding the ability to add such function? Like:
>>
>> procedure(LIST_LENGTH list)
>> list(LENGTH list length)
>> return(${length})
>> endprocedure()
>
> We don't have a syntax for
23 matches
Mail list logo