Re: [CMake] CMake, QT5 and cross compilation

[Dave Flogeras]

On Thu, Dec 17,
>
> So, here is my question: How can I overwrite the moc-executable (and uic
> etc) path to use another moc version than the one found by the
> find_package mechanism? If I use the moc which is part of my Linux host
> PC rather than the arm compiled moc in the Raspberry file system, the
> code generation should be fine, and afterwards, I will link against the
> Raspberry Pi Qt5 libraries.
>

Hi Hauke,

In the past, I have done this (wth Qt4) by generating, then hand
editing the CMakeCache.txt to change the location of the moc
executable to the native one.  Now that reading your post made me
re-visit this it seems to have two problems.  First, with Qt5 finder,
it doesn't seem to expose the moc location in the cache.  Also I
recall doing it the way I described works only if your native version
is exactly the same as the arm version, otherwise you get errors like
"this header was generated with a different version of Qt"  It
always seemed pretty brittle.

Another way that I do this, is by generating a toolchain file, which
forces cmake to look only inside the RPi root directory.  This means
it will find the cross compiled moc executable.  Then I have qemu set
up with the Linux binfmt driver so that I can execute arm binaries
'natively'..  This is not trivial, and requires setting up a wrapper
so that qemu can find the arm linker-loader etc. but you may be able
to use this as a solution.  I (loosely) followed this guide, modifying
the wrapper to my system.

https://gentoo-handbook.lugons.org/proj/en/base/embedded/handbook/index.xml?style=printable=1=5

Good luck.

I'd also like to hear if there is a different solution to this problem.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Tests with assert and Release build type

[Magnus Therning]

Dave Flogeras writes:

> On Fri, Dec 18, 2015 at 9:55 AM, Magnus Therning  wrote:
>>
>> I'm sure I'm not the first one to run into the conflict between a
>> desire to test the code shipped to customers and the desire to at the
>> same time define NDEBUG to make sure tests don't have their `assert`
>> turned into NOOPs.
>>
>> Is there some nice way of handling this?
>
> I've also wondered this. My solution of choice has always been to keep
> my tests in a subdirectory with a test header like you described:
>
> 
> #fidef NDEBUG
>  #undef NDEBUG
>  #include  // or assert.h for C
>  #define NDEBUG
> #else
>  #include 
> #endif
> 
>
> And include this in each of the unit tests. However, I have found
> sometimes this is not foolproof. In particular I recall on one version
> of OSX one of the system headers would undo this and make assert()
> disappear again, requiring me to play the #include shell game. I
> usually place my "test_assert.hpp" include after all others in the
> unit test, but this is brittle.
>
> I have always just left it as a "good enough" solution, but I too
> would love to hear if someone has a more robust solution.

I did a bit of testing and found that

1. CMAKE_C_FLAGS_* is, very irritatingly, *not* a list, so it's not easy
to remove '-DNDEBUG' from them in the CMakeLists.txt for the tests.

2. Compile options added by target_compile_options() are added *after*
CMAKE_C_FLAGS_* so I settled on using it to pass -UNDEBUG to gcc.

Far from nice, but it works for now (which feels quite typical for CMake).

/M

--
Magnus Therning  OpenPGP: 0x927912051716CE39
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus

If you can explain how you do something, then you're very very bad at
it.
 -- John Hopfield


signature.asc
Description: PGP signature
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Tests with assert and Release build type

[Magnus Therning]

Ruslan Baratov writes:

> How about using RelWithDebInfo? See:
> http://stackoverflow.com/a/28124715/2288008

Hmm, I'm probably missing something but how does that solve the issue
with some targets requiring NDEBUG to be *undefined* and other targets
requiring NDEBUG to be defined?

/M

> On 18-Dec-15 20:55, Magnus Therning wrote:
>> I'm sure I'm not the first one to run into the conflict between a desire
>> to test the code shipped to customers and the desire to at the same time
>> define NDEBUG to make sure tests don't have their `assert` turned into
>> NOOPs.
>>
>> Is there some nice way of handling this?
>>
>> I can always remove -DNDEBUG from the CFLAGS for tests (possibly by
>> defining a new macro, `ADD_EXECUTABLE_TEST()` or something). Another
>> option is to `#undef NDEBUG` in the source of tests.
>>
>> If there's some more or less standard way to address this I'd like to
>> use that.
>>
>> /M
>>
>> --
>> Magnus Therning  OpenPGP: 0x927912051716CE39
>> email: mag...@therning.org   jabber: mag...@therning.org
>> twitter: magthe   http://therning.org/magnus
>>
>> There's a big difference between making something easy to use and
>> making it productive.
>>   -- Adam Bosworth
>>
>>


--
Magnus Therning  OpenPGP: 0x927912051716CE39
email: mag...@therning.org   jabber: mag...@therning.org
twitter: magthe   http://therning.org/magnus

C++ is history repeated as tragedy. Java is history repeated as farce.
 -- Scott McKay


signature.asc
Description: PGP signature
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [cmake-developers] Create subdirectories in Resource directory for Frameworks and Application bundle.

[Ruslan Baratov via cmake-developers]

On 18-Dec-15 22:46, Bartosz Kosiorek wrote:


Thank you all for your tips/advice.


From our experience IDE generators (eg. Visual Studio, Xcode) is 
much slower than Make or Ninja. I will attach benchmarks later.



Unfortunately I'm unable to build Universal libraries for x86 and arm 
architectures by using Makefile.


This feature will work only for Xcode. For Makefile generator 
variable/property IOS_INSTALL_COMBINED is ignored. Xcode and Makefile 
differs in internals. Xcode can hold in build directory all variants of 
library like Release/Debug + Simulator/Device:


Debug-iphoneos/libfoo.a # xcodebuild -sdk iphoneos -config Debug
Debug-iphonesimulator/libfoo.a # xcodebuild -sdk iphonesimulator -config 
Debug

Release-iphoneos/libfoo.a # xcodebuild -sdk iphoneos -config Release
Release-iphonesimulator/libfoo.a # xcodebuild -sdk iphonesimulator 
-config Release


Makefile holds only one variant so building both Simulator/Device in one 
project is tricky. You can build/install several libraries by Makefile 
and combine them with lipo using some external script.



See attached logs.


It seems that two different SDK's (iPhoneOS and iPhoneSimulator) needs 
to be used in that case.


Do you know how it could be fixed?

Maybe I should add "CMAKE_OSX_SYSROOT "iphoneos" support for other 
generators?


What do you think about that idea?


Thanks in advance

Bartosz​


PS

I'm attaching the script which I'm using for testing purposes.

To reproduce it just run command (from command line):

   cd builddir && cmake .. && cmake --build .




*From:*Ruslan Baratov [mailto:ruslan_bara...@yahoo.com]
*Sent:* Saturday, December 12, 2015 6:49 AM
*To:* Bartosz Kosiorek
*Cc:* Clinton Stimpson; Gregor Jasny; CMake Developers
*Subject:* Re: [cmake-developers] Create subdirectories in Resource 
directory for Frameworks and Application bundle.


On 12-Dec-15 10:08, Bartosz Kosiorek wrote:

Thanks Ruslan.

I would like to create instruction which is universal for all
generators.

I think it's not possible. E.g. IOS_INSTALL_COMBINED will work only 
for Xcode.



Currently we would like to support both Make/Ninja and Xcode generators,

...


because Make is much faster than Xcode generator, and we are using it 
in our CI system.


Do you mean generate step or build? I've used to compile quite big 
projects like OpenCV with Xcode and according to the `top` it uses all 
my cores with clang++ at 100% CPU time.
Can you show any benchmarks? Also note that Xcode can add some 
additional stuff, like dSYM: 
https://github.com/headupinclouds/gatherer/pull/69



Make is also common for other architectures (Linux, QNX, Android etc.)

Unfortunately

   set(CMAKE_OSX_SYSROOT "iphoneos")

is not working for me.

It displays error:

  /Users/warsaw/Perforce/cmake-dev/cmake-build/bin/cmake .. && 
/Users/warsaw/Perforce/cmake-dev/cmake-build/bin/cmake --build .


  -- Configuring done

  -- Generating done

  -- Build files have been written to: 
/Users/warsaw/Perforce/cmake_ios_framework_with_resource2/builddir


  [ 14%] Building C object 
shared_empty/heymath/CMakeFiles/heymath.dir/add.c.o


  clang: warning: no such sysroot directory: 'iphoneos'

...

Do you have some tip for that?

Yes, this hint was for Xcode generator.


After removing "-isysroot ${CMAKE_OSX_SYSROOT}" everything works 
perfectly. Thanks


Unfortunately CMAKE_XCODE_ATTRIBUTE_IPHONEOS_DEPLOYMENT_TARGET is not 
working with Make.


Is it possible to introduce CMAKE_IOS_DEPLOYMENT_TARGET, as we already 
have CMAKE_OSX_DEPLOYMENT_TARGET?


Since OSX_ARCHITECTURES controls iOS architectures too I think request 
should sounds like "Extend OSX_DEPLOYMENT_TARGET property for iOS 
platform".




I have attached my example script which I'm using.

​Could you please modify it to be better (and still support other 
generators)?


I don't know how to use iOS target with Makefile generator.

Some notes about project you've sent:
* You need to add instructions to codesign your bundle
* Instead of hardcoding `set(CMAKE_OSX_SYSROOT 
"/Applications/Xcode.app/.../iPhoneSimulator.sdk")` you can run 
`xcode-select -print-path` to detect location of default Xcode version
* Should be `set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} 
-mios-version-min=8.0")` instead of `set(CMAKE_CXX_FLAGS 
"-mios-version-min=8.0")` otherwise some flags may be lost


Ruslan

Best Regards

Bartosz



*From:*Ruslan Baratov 


*Sent:* Saturday, December 12, 2015 1:58 AM
*To:* Bartosz Kosiorek
*Cc:* clin...@elemtech.com; Gregor Jasny; 
CMake Developers
*Subject:* Re: [cmake-developers] Create subdirectories in Resource 
directory for Frameworks and Application bundle.


On 12-Dec-15 03:46, Bartosz Kosiorek wrote:

Hi

To enable iOS build, I'm using following settings in CMakeLists.txt:

set(APPLE_PLATFORM "iphonesimulator")

I think this 

Re: [CMake] Tests with assert and Release build type

[Dave Flogeras]

On Fri, Dec 18, 2015 at 9:55 AM, Magnus Therning  wrote:
>
> I'm sure I'm not the first one to run into the conflict between a desire
> to test the code shipped to customers and the desire to at the same time
> define NDEBUG to make sure tests don't have their `assert` turned into
> NOOPs.
>
> Is there some nice way of handling this?

I've also wondered this.  My solution of choice has always been to
keep my tests in a subdirectory with a test header like you described:


#fidef NDEBUG
 #undef NDEBUG
 #include  // or assert.h for C
 #define NDEBUG
#else
 #include 
#endif


And include this in each of the unit tests.  However, I have found
sometimes this is not foolproof.  In particular I recall on one
version of OSX one of the system headers would undo this and make
assert() disappear again, requiring me to play the #include shell
game.  I usually place my "test_assert.hpp" include after all others
in the unit test, but this is brittle.

I have always just left it as a "good enough" solution, but I too
would love to hear if someone has a more robust solution.
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] build order

[Owen Hogarth II]

Hi David

Thank you for the response, I thought that I was doing something wrong. I
mean it's documented and I followed the docs as close as possible to write
my scripts but there's literally no mention about how to solve this
external/ internal project setup in the official docs.

I saw some things online but I honestly it seemed overly complicated and
really prone to breaking.

I'll edit my project to make them all external projects and work from that
angle.

Thanks

On Sat, Dec 19, 2015 at 9:18 PM, David Cole  wrote:

> Build the second thing as an ExternalProject, too, and use the DEPENDS
> keyword to make it build after the first thing.
>
> Don't try to mix-and-match external projects and non-external projects in
> the same CMake configure... It's just too much work to get things working
> in a reasonable cross-platform way. It's possible, but certainly not easy.
>
>
> David
>
>
> > On Dec 18, 2015, at 3:29 PM, Owen Hogarth II 
> wrote:
> >
> > If you download, compile and install a cmake project through external
> project
> >
> > How can I make sure that the external project is built before something
> that depends on that external project?
> > --
> >
> > Powered by www.kitware.com
> >
> > Please keep messages on-topic and check the CMake FAQ at:
> http://www.cmake.org/Wiki/CMake_FAQ
> >
> > Kitware offers various services to support the CMake community. For more
> information on each offering, please visit:
> >
> > CMake Support: http://cmake.org/cmake/help/support.html
> > CMake Consulting: http://cmake.org/cmake/help/consulting.html
> > CMake Training Courses: http://cmake.org/cmake/help/training.html
> >
> > Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
> >
> > Follow this link to subscribe/unsubscribe:
> > http://public.kitware.com/mailman/listinfo/cmake
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[cmake-developers] [CMake 0015889]: IA64 compilers not found in Visual Studio 2010 (and probably others)

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=15889 
== 
Reported By:Vivien
Assigned To:
== 
Project:CMake
Issue ID:   15889
Category:   CMake
Reproducibility:always
Severity:   major
Priority:   high
Status: new
== 
Date Submitted: 2015-12-19 16:00 EST
Last Modified:  2015-12-19 16:00 EST
== 
Summary:IA64 compilers not found in Visual Studio 2010 (and
probably others)
Description: 
In the CMakeDetermineCompilerId at line 186 there is :

set(id_platform ia64)

this leads to generate a bad CompilerIdC(XX).vcxproj with Debug|ia64 and
Release|ia64 configurations, not recognized by devenv.exe. 
Indeed devenv.exe onyl recognize "Itanium". 
The question is why changing "Itanium" to "ia64" in the .cmake because without
this line everything goes well and the IA compilers are found 

Steps to Reproduce: 
Try to configure any CMake project with Visual Studio 2010 IA64, and compilers
won't be found.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-12-19 16:00 Vivien New Issue
==

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

[Cmake-commits] CMake branch, master, updated. v3.4.1-736-g693a42f

[Kitware Robot]

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  693a42fb00650180c98a15a62e11e450b6ab99f0 (commit)
  from  a5149d31beaf7e36c449659066f534813a8c (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -
https://cmake.org/gitweb?p=cmake.git;a=commitdiff;h=693a42fb00650180c98a15a62e11e450b6ab99f0
commit 693a42fb00650180c98a15a62e11e450b6ab99f0
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Sun Dec 20 00:01:16 2015 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Sun Dec 20 00:01:16 2015 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index 99c621a..85a752e 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 4)
-set(CMake_VERSION_PATCH 20151219)
+set(CMake_VERSION_PATCH 20151220)
 #set(CMake_VERSION_RC 1)

---

Summary of changes:
 Source/CMakeVersion.cmake |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)


hooks/post-receive
-- 
CMake
___
Cmake-commits mailing list
Cmake-commits@cmake.org
http://public.kitware.com/mailman/listinfo/cmake-commits

Re: [CMake] build order

[David Cole via CMake]

Build the second thing as an ExternalProject, too, and use the DEPENDS keyword 
to make it build after the first thing.

Don't try to mix-and-match external projects and non-external projects in the 
same CMake configure... It's just too much work to get things working in a 
reasonable cross-platform way. It's possible, but certainly not easy.


David


> On Dec 18, 2015, at 3:29 PM, Owen Hogarth II  wrote:
> 
> If you download, compile and install a cmake project through external project
> 
> How can I make sure that the external project is built before something that 
> depends on that external project?
> -- 
> 
> Powered by www.kitware.com
> 
> Please keep messages on-topic and check the CMake FAQ at: 
> http://www.cmake.org/Wiki/CMake_FAQ
> 
> Kitware offers various services to support the CMake community. For more 
> information on each offering, please visit:
> 
> CMake Support: http://cmake.org/cmake/help/support.html
> CMake Consulting: http://cmake.org/cmake/help/consulting.html
> CMake Training Courses: http://cmake.org/cmake/help/training.html
> 
> Visit other Kitware open-source projects at 
> http://www.kitware.com/opensource/opensource.html
> 
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/cmake
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

[cmake-developers] [CMake 0015888]: No FindGTK3.cmake by default

[Mantis Bug Tracker]

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=15888 
== 
Reported By:Ignat Loskutov
Assigned To:
== 
Project:CMake
Issue ID:   15888
Category:   Modules
Reproducibility:always
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2015-12-19 09:44 EST
Last Modified:  2015-12-19 09:44 EST
== 
Summary:No FindGTK3.cmake by default
Description: 
For some reason, there is no FindGTK3 module yet, while FindGTK2 and FindGTK
(last probably only used by https://cmake.org/Bug/view.php?id=41#c1.5
retrogrades) exist. It makes many developers re-invent FindGTK3 again and again,
while it could be provided with CMake by default instead.

Additional Information: 
Examples of existing FindGTK3.cmake:
https://github.com/eiskaltdcpp/eiskaltdcpp/blob/master/cmake/FindGTK3.cmake —
a clone of FindGTK2.cmake
https://chromium.googlesource.com/external/Webkit/+/master/Source/cmake/FindGTK3.cmake
— PkgConfig-based solution
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2015-12-19 09:44 Ignat Loskutov New Issue
==

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake-developers

Re: [CMake] Feature request: expose curl to cmake -E

[iosif neitzke]

Mostly yes.

On Sat, Dec 19, 2015 at 8:45 AM, Greg Marr  wrote:
> iosif neitzke wrote:
>>On Fri, Dec 18, 2015 at 2:18 PM, Jakob van Bethlehem 
>> wrote:
>>> Depending on what you precisely wish to achieve, maybe file(DOWNLOAD) 
>>> already fits your needs?
>>> https://cmake.org/cmake/help/v3.1/command/file.html
>>
>>It does, generally, in the way that ExternalProject also fits, but I think 
>>would require writing wrapper >scripts.  My specific use case was something 
>>like:
>>
>>cmake -E curl http://jenkins/buildA/artifacts/stuff.tar
>>cmake -E tar xzf stuff.tar
>>cmake -Hstuff/path/to/CMakeLists/ -Bbuild_dir cmake --build build_dir
>>
>>I thought 'curl' is sort of at the level of 'tar', in being a useful tool that
>>could be exposed fairly easily in a cmake portable command.
>>Those portable commands are another thing that CMake offers that makes working
>>on Windows a little easier, if you don't already have Cygwin or the like.
>
> curl is already portable.  Are you just trying to avoid installing curl?
>
-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Feature request: expose curl to cmake -E

[Jakob van Bethlehem]

> 
> I thought 'curl' is sort of at the level of 'tar', in being a useful
> tool that could be exposed fairly easily in a cmake portable command.

Have you ever checked out the full man page of curl and the full feature list? 
(http://curl.haxx.se/docs/manpage.html)
This is certainly not ‘easy’ to simply port ;-)

Sincerely,
Jakob

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake

Re: [CMake] Feature request: expose curl to cmake -E

[Greg Marr]

iosif neitzke wrote:
>On Fri, Dec 18, 2015 at 2:18 PM, Jakob van Bethlehem 
> wrote:
>> Depending on what you precisely wish to achieve, maybe file(DOWNLOAD) 
>> already fits your needs?
>> https://cmake.org/cmake/help/v3.1/command/file.html
>
>It does, generally, in the way that ExternalProject also fits, but I think 
>would require writing wrapper >scripts.  My specific use case was something 
>like:
>
>cmake -E curl http://jenkins/buildA/artifacts/stuff.tar
>cmake -E tar xzf stuff.tar
>cmake -Hstuff/path/to/CMakeLists/ -Bbuild_dir cmake --build build_dir
>
>I thought 'curl' is sort of at the level of 'tar', in being a useful tool that
>could be exposed fairly easily in a cmake portable command.
>Those portable commands are another thing that CMake offers that makes working
>on Windows a little easier, if you don't already have Cygwin or the like.

curl is already portable.  Are you just trying to avoid installing curl?

-- 

Powered by www.kitware.com

Please keep messages on-topic and check the CMake FAQ at: 
http://www.cmake.org/Wiki/CMake_FAQ

Kitware offers various services to support the CMake community. For more 
information on each offering, please visit:

CMake Support: http://cmake.org/cmake/help/support.html
CMake Consulting: http://cmake.org/cmake/help/consulting.html
CMake Training Courses: http://cmake.org/cmake/help/training.html

Visit other Kitware open-source projects at 
http://www.kitware.com/opensource/opensource.html

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/cmake