Re: [CMake] Deploy Qt based App to WindowsStore using CMake

2016-03-03 Thread Nikita Barawade 


Hi,

Thank you for reply !
Yes , I have the developer mode under Windows 10 activated.
I can see  AppxManifest.xml present inside ,Sample_App\Build\Debug\AppX\

With below link i.e using qmake to covert Qt project to WinRT compatible, I can 
get App running on both "Remote machine" and "Local Machine" .
But I want it to be done using cmake only.

https://doc-snapshots.qt.io/qt5-5.6/winrt-support.html#building-from-source
Qt for WinRT | Qt 
5.6
doc-snapshots.qt.io
If you are targeting a remote device, please follow all instructions by Visual 
Studio to set it up correctly. If you are targeting an emulator for Windows 
Phone ...






Regards,
​Nikita​



From: Roman Wüger 
Sent: 04 March 2016 01:39 AM
To: Nikita Barawade
Cc: cmake@cmake.org
Subject: Re: [CMake] Deploy Qt based App to WindowsStore using CMake

Do you have the developer mode under Windows 10 activated?
Do you have registered your app (Add-AppxPackage -Register AppxManifest.xml)?
See https://doc-snapshots.qt.io/qt5-5.6/winrt-support.html#building-from-source

Qt for WinRT | Qt 
5.6
doc-snapshots.qt.io
If you are targeting a remote device, please follow all instructions by Visual 
Studio to set it up correctly. If you are targeting an emulator for Windows 
Phone ...



Best regards
Roman

Am 03.03.2016 um 16:53 schrieb Nikita Barawade 
>:




Hi,

I have application based on Qt UI . My aim is to convert this app to run on 
WindowsStore.

Project has been converted to Universal Windows and building  without errors.
Project is using Qt version 5.6 for WInRT.
Here is a command used ,

cmake .. -G "Visual Studio 14 2015" -DCMAKE_SYSTEM_NAME=WindowsStore 
-DCMAKE_SYSTEM_VERSION=10.0

Target Architecture is x86.

The problem comes when I try to deploy it on Local or remote machine.


 i.e Unable to activate Windows Store app ...
The sampleApp.exe process started but the activation request failed with error 
"The app didn't start"

I have already gone throgh these links :
http://stackoverflow.com/questions/13404315/unable-to-activate-windows-store-app
http://stackoverflow.com/questions/19847563/unable-to-activate-windows-store-app-the-app-didnt-start
http://blogs.technet.com/b/askperf/archive/2013/10/11/what-to-do-if-your-windows-8-modern-app-fails-to-start.aspx
c# - Unable to activate windows store app the app didn't 
...
stackoverflow.com
First of all I would like to say that I already tried all the solutions I could 
find on the internet, including Unable to Activate Windows Store App I recently 
...



http://irisclasson.com/2012/11/04/problem-unable-to-activate-windows-store-app-the-app1-exe-process-started-but-the-activation-request-failed-with-error-the-app-didnt-start/
Problem: Unable to activate Windows Store app: The App1 
...
irisclasson.com
Thanks, this really helped! The other solutions I found weren’t applicable for 
me, but this was just what I needed.



visual studio - Unable to Activate Windows Store App 
...
stackoverflow.com
I installed a retail version of Windows 8 Pro. I downloaded and installed 
Visual Studio Express 2012. I asked for and received a developers certificate. 
Then I tried ...



If anyone has tried it before ? Please guide.


Regards,
Nikita
*
 eInfochips Business Disclaimer: This e-mail message and all attachments 
transmitted with it are intended solely for the use of the addressee and may 
contain legally privileged and confidential information. If the reader of this 
message is not the intended recipient, or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, or other use of this message or its 
attachments is strictly prohibited. If you have received this message in error, 
please notify the sender immediately by replying to this message and please 
delete it from your computer. Any views expressed in this message are those of 
the individual sender unless otherwise stated. Company has taken enough 
precautions to prevent the spread of viruses. However the company accepts no 
liability for any damage caused by any virus transmitted by this email.

Re: [CMake] Problem using VS-compiled Clang as a C/C++ compiler.

2016-03-03 Thread Cristian Adam 
Hi Anton,

clang.exe doesn't know of any windows specific things.  Clang-cl instead
does.

Just make sure to have clang-cl before msvc-cl in path and ninja will just
work.

Cheers,
Cristian
On Mar 4, 2016 01:31, "Anton Yartsev"  wrote:

> Hi all,
>
> I'm trying to use Clang, compiled with VS 2013 (configuration:Release,
> platform:x64) as a C/C++ compiler for a simple HelloWorld CMake project.
> Generation ends up with errors like "clang.exe: error: no such file or
> directory: '/DWIN32'" at compiler check stage. If I understand correctly
> the problem is that MSVC compiler options are fed to Clang for some reason
> (maybe the "-- The C compiler identification is unknown" log entry is
> related to the problem?).
> Could anyone help to resolve this, please?
>
> I also tried to change compiler ID with "-DCMAKE_C_COMPILER_ID=Clang
> -DCMAKE_CXX_COMPILER_ID=Clang", then compilation succeeded, but linkage
> failed (just as described in the thread "Question on usage of cmake on
> Windows with clang"
> http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/54650).
> Here the problem seems to be reversed: GNU linker options are fed to MS
> linker.
>
> ** Setup and details:
> 1) INCLUDE and PATH set to clang/clang-cl
> 2) command line environment is configured with vsvars32.bat
> 3) CC and CXX set to clang
>
> $ cat CMakeLists.txt
> project(test_project)
> add_executable(main file.cpp)
>
> $ cmake -G "Ninja" -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang ..
>
> Log:
> -- The C compiler identification is unknown
> -- The CXX compiler identification is Clang 3.7.1
> -- Check for working C compiler using: Ninja
> -- Check for working C compiler using: Ninja -- broken
> CMake Error at C:/Program
> Files/CMake/share/cmake-3.5/Modules/CMakeTestCCompiler.cmake:61 (message):
>   The C compiler "D:/-Work-/llvm-3.7.1.src/-VS_build VS
>   2013-/Release/bin/clang.exe" is not able to compile a simple test
> program.
>   It fails with the following output:
>Change Dir: D:/-Work-/llvm-3.7.1.src/-CLANG-/CMakeFiles/CMakeTmp
>
>   Run Build Command:"C:/PROGRA~1/ninja/ninja.exe" "cmTC_2cb9d"
>
>   [1/2] Building C object CMakeFiles\cmTC_2cb9d.dir\testCCompiler.c.obj
>
>   FAILED: D:\-Work-\LLVM-3~2.SRC\-VS_BU~2\Release\bin\clang.exe /DWIN32
>   /D_WINDOWS /W3 -o CMakeFiles\cmTC_2cb9d.dir\testCCompiler.c.obj -c
>   testCCompiler.c
>
>   clang.exe: error: no such file or directory: '/DWIN32'
>   clang.exe: error: no such file or directory: '/D_WINDOWS'
> ...
>
> OS: Windows 7 (x64)
>
> clang version 3.7.1 (tags/RELEASE_371/final)
> Target: x86_64-pc-windows-msvc
> Thread model: posix
>
> cmake version 3.5.0-rc3
>
> Thank you!
>
> --
> Anton
>
> --
>
> 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-commits] CMake branch, master, updated. v3.5.0-rc3-158-g8318016

2016-03-03 Thread 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  831801671c247a219a5c2bf785d7c62b6cdf3e61 (commit)
  from  f37f422a7fa062c3d744d0e82752839ab7f89b06 (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=831801671c247a219a5c2bf785d7c62b6cdf3e61
commit 831801671c247a219a5c2bf785d7c62b6cdf3e61
Author: Kitware Robot <kwro...@kitware.com>
AuthorDate: Fri Mar 4 00:01:03 2016 -0500
Commit: Kitware Robot <kwro...@kitware.com>
CommitDate: Fri Mar 4 00:01:03 2016 -0500

CMake Nightly Date Stamp

diff --git a/Source/CMakeVersion.cmake b/Source/CMakeVersion.cmake
index e82aec5..d19f965 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 5)
-set(CMake_VERSION_PATCH 20160303)
+set(CMake_VERSION_PATCH 20160304)
 #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

[cmake-developers] [CMake 0016005]: Add basic support for generating .pc files.

2016-03-03 Thread Mantis Bug Tracker 

The following issue has been SUBMITTED. 
== 
https://cmake.org/Bug/view.php?id=16005 
== 
Reported By:James Tocknell
Assigned To:
== 
Project:CMake
Issue ID:   16005
Category:   (No Category)
Reproducibility:N/A
Severity:   feature
Priority:   normal
Status: new
== 
Date Submitted: 2016-03-03 23:57 EST
Last Modified:  2016-03-03 23:57 EST
== 
Summary:Add basic support for generating .pc files.
Description: 
The following files add basic support for creating pkg-config files for
libraries from cmake.
== 

Issue History 
Date ModifiedUsername   FieldChange   
== 
2016-03-03 23:57 James Tocknell New Issue
2016-03-03 23:57 James Tocknell File Added: pkgconfig.tar.gz
==

-- 

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] Problem using VS-compiled Clang as a C/C++ compiler.

2016-03-03 Thread Anton Yartsev 

Hi all,

I'm trying to use Clang, compiled with VS 2013 (configuration:Release, 
platform:x64) as a C/C++ compiler for a simple HelloWorld CMake project. 
Generation ends up with errors like "clang.exe: error: no such file or 
directory: '/DWIN32'" at compiler check stage. If I understand correctly 
the problem is that MSVC compiler options are fed to Clang for some 
reason (maybe the "-- The C compiler identification is unknown" log 
entry is related to the problem?).

Could anyone help to resolve this, please?

I also tried to change compiler ID with "-DCMAKE_C_COMPILER_ID=Clang 
-DCMAKE_CXX_COMPILER_ID=Clang", then compilation succeeded, but linkage 
failed (just as described in the thread "Question on usage of cmake on 
Windows with clang" 
http://thread.gmane.org/gmane.comp.programming.tools.cmake.user/54650). 
Here the problem seems to be reversed: GNU linker options are fed to MS 
linker.


** Setup and details:
1) INCLUDE and PATH set to clang/clang-cl
2) command line environment is configured with vsvars32.bat
3) CC and CXX set to clang

$ cat CMakeLists.txt
project(test_project)
add_executable(main file.cpp)

$ cmake -G "Ninja" -DCMAKE_C_COMPILER=clang -DCMAKE_CXX_COMPILER=clang ..

Log:
-- The C compiler identification is unknown
-- The CXX compiler identification is Clang 3.7.1
-- Check for working C compiler using: Ninja
-- Check for working C compiler using: Ninja -- broken
CMake Error at C:/Program 
Files/CMake/share/cmake-3.5/Modules/CMakeTestCCompiler.cmake:61 (message):

  The C compiler "D:/-Work-/llvm-3.7.1.src/-VS_build VS
  2013-/Release/bin/clang.exe" is not able to compile a simple test 
program.

  It fails with the following output:
   Change Dir: D:/-Work-/llvm-3.7.1.src/-CLANG-/CMakeFiles/CMakeTmp

  Run Build Command:"C:/PROGRA~1/ninja/ninja.exe" "cmTC_2cb9d"

  [1/2] Building C object CMakeFiles\cmTC_2cb9d.dir\testCCompiler.c.obj

  FAILED: D:\-Work-\LLVM-3~2.SRC\-VS_BU~2\Release\bin\clang.exe /DWIN32
  /D_WINDOWS /W3 -o CMakeFiles\cmTC_2cb9d.dir\testCCompiler.c.obj -c
  testCCompiler.c

  clang.exe: error: no such file or directory: '/DWIN32'
  clang.exe: error: no such file or directory: '/D_WINDOWS'
...

OS: Windows 7 (x64)

clang version 3.7.1 (tags/RELEASE_371/final)
Target: x86_64-pc-windows-msvc
Thread model: posix

cmake version 3.5.0-rc3

Thank you!

--
Anton

--

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] Appending to LINK_FLAGS property of a target doesn't seem to work correctly

2016-03-03 Thread Nils Gladitz 

On 03.03.2016 22:57, Dan Liew wrote:

Hi,

I noticed recently is you do something like this

add_executable(foo a.cpp b.cpp)
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-fopenmp")
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-static")

then the flags that end up being passed to the compiler during linking
are like this.

gcc -g -O0 -fopenmp;-static

It looks like when using the property with APPEND it becomes a list
but when emitted the list isn't expanded properly. I noticed this
using CMake 3.4.3 using the "Unix Makefile" generator.

Is this intentional or is this a bug?


LINK_FLAGS is not a list property; flags have to be whitespace separated.
You can use APPEND_STRING instead of APPEND for this.

Nils
--

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] [cmake-developers] Appending to LINK_FLAGS property of a target doesn't seem to work correctly

2016-03-03 Thread Nils Gladitz 

On 03.03.2016 22:57, Dan Liew wrote:

Hi,

I noticed recently is you do something like this

add_executable(foo a.cpp b.cpp)
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-fopenmp")
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-static")

then the flags that end up being passed to the compiler during linking
are like this.

gcc -g -O0 -fopenmp;-static

It looks like when using the property with APPEND it becomes a list
but when emitted the list isn't expanded properly. I noticed this
using CMake 3.4.3 using the "Unix Makefile" generator.

Is this intentional or is this a bug?


LINK_FLAGS is not a list property; flags have to be whitespace separated.
You can use APPEND_STRING instead of APPEND for this.

Nils
--

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] Appending to LINK_FLAGS property of a target doesn't seem to work correctly

2016-03-03 Thread Dan Liew 
Hi,

I noticed recently is you do something like this

add_executable(foo a.cpp b.cpp)
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-fopenmp")
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-static")

then the flags that end up being passed to the compiler during linking
are like this.

gcc -g -O0 -fopenmp;-static

It looks like when using the property with APPEND it becomes a list
but when emitted the list isn't expanded properly. I noticed this
using CMake 3.4.3 using the "Unix Makefile" generator.

Is this intentional or is this a bug?

Thanks,
Dan.
-- 

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] Appending to LINK_FLAGS property of a target doesn't seem to work correctly

2016-03-03 Thread Dan Liew 
Hi,

I noticed recently is you do something like this

add_executable(foo a.cpp b.cpp)
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-fopenmp")
set_property(TARGET shell APPEND PROPERTY LINK_FLAGS "-static")

then the flags that end up being passed to the compiler during linking
are like this.

gcc -g -O0 -fopenmp;-static

It looks like when using the property with APPEND it becomes a list
but when emitted the list isn't expanded properly. I noticed this
using CMake 3.4.3 using the "Unix Makefile" generator.

Is this intentional or is this a bug?

Thanks,
Dan.
-- 

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] Deploy Qt based App to WindowsStore using CMake

2016-03-03 Thread Roman Wüger 
Do you have the developer mode under Windows 10 activated?
Do you have registered your app (Add-AppxPackage -Register AppxManifest.xml)?
See https://doc-snapshots.qt.io/qt5-5.6/winrt-support.html#building-from-source

Best regards
Roman 

> Am 03.03.2016 um 16:53 schrieb Nikita Barawade 
> :
> 
> 
> 
> Hi,
> 
> I have application based on Qt UI . My aim is to convert this app to run on 
> WindowsStore.
> 
> Project has been converted to Universal Windows and building  without errors.
> Project is using Qt version 5.6 for WInRT.
> Here is a command used ,
> 
> cmake .. -G "Visual Studio 14 2015" -DCMAKE_SYSTEM_NAME=WindowsStore 
> -DCMAKE_SYSTEM_VERSION=10.0
> 
> Target Architecture is x86. 
> 
> The problem comes when I try to deploy it on Local or remote machine.
> 
>  
>  i.e Unable to activate Windows Store app ...
> The sampleApp.exe process started but the activation request failed with 
> error "The app didn't start"
> 
> I have already gone throgh these links :
> http://stackoverflow.com/questions/13404315/unable-to-activate-windows-store-app
> http://stackoverflow.com/questions/19847563/unable-to-activate-windows-store-app-the-app-didnt-start
> http://blogs.technet.com/b/askperf/archive/2013/10/11/what-to-do-if-your-windows-8-modern-app-fails-to-start.aspx
> 
> c# - Unable to activate windows store app the app didn't ...
> stackoverflow.com
> First of all I would like to say that I already tried all the solutions I 
> could find on the internet, including Unable to Activate Windows Store App I 
> recently ...
> 
> 
> http://irisclasson.com/2012/11/04/problem-unable-to-activate-windows-store-app-the-app1-exe-process-started-but-the-activation-request-failed-with-error-the-app-didnt-start/
> 
> Problem: Unable to activate Windows Store app: The App1 ...
> irisclasson.com
> Thanks, this really helped! The other solutions I found weren’t applicable 
> for me, but this was just what I needed.
> 
> 
>  
> visual studio - Unable to Activate Windows Store App ...
> stackoverflow.com
> I installed a retail version of Windows 8 Pro. I downloaded and installed 
> Visual Studio Express 2012. I asked for and received a developers 
> certificate. Then I tried ...
> 
> 
> If anyone has tried it before ? Please guide.
> 
> 
> Regards,
> Nikita
> *
>  eInfochips Business Disclaimer: This e-mail message and all attachments 
> transmitted with it are intended solely for the use of the addressee and may 
> contain legally privileged and confidential information. If the reader of 
> this message is not the intended recipient, or an employee or agent 
> responsible for delivering this message to the intended recipient, you are 
> hereby notified that any dissemination, distribution, copying, or other use 
> of this message or its attachments is strictly prohibited. If you have 
> received this message in error, please notify the sender immediately by 
> replying to this message and please delete it from your computer. Any views 
> expressed in this message are those of the individual sender unless otherwise 
> stated. Company has taken enough precautions to prevent the spread of 
> viruses. However the company accepts no liability for any damage caused by 
> any virus transmitted by this email. 
> *
> -- 
> 
> 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

Re: [CMake] fixup_bundle on Windows : issue with multiple exe applications

2016-03-03 Thread David Cole via CMake 
It was designed originally with the assumption that all the
executables in a bundle are in the same directory. If you violate that
assumption, I don't think you can count on it to do the right thing
100% of the time.

If it works for you calling it multiple times with deepest first, then
maybe you can get lucky...

I would definitely dig into it and understand exactly what it's doing,
though, if you want to make sure it's going to continue working for
your scenario.


HTH,
David C.


On Thu, Mar 3, 2016 at 1:43 PM, Benjamin Ballet  wrote:
> Hello
>
> I'd like to discuss a problem I encountered today with the very useful
> module BundleUtilities
>
> We have an application on Windows with one main exe file in the top folder
> and a few other exe in subdirectories, like that :
>
> applicationfolder  \
>   | main.exe
>   | toolsfolder \
> | supertoolfolder \
> |
> supertool.exe
> | toptoolfolder \
>  |
> toptool.exe
>
> But if I simply call
> fixup_bundle("applicationfolder/main.exe" plugins libs)
>
> the verify_app will fails.
>
> Just a reminder that there is no rpath on Windows : dll must be either in
> PATH or in the same folder or in the working directory.
>
> We expected fixup_bundle to copy the required dll for main.exe in
> applicationfolder, the required dll for supertool.exe in supertoolfolder and
> the required dll for toptool.exe in toptoolfolder, but it acually didn't
> copied anything in supertoolfolder and toptoolfolder.
>
> I worked around this issue by calling fixup_bundle multiple time with the
> following order : (the deepest exes first)
>
> fixup_bundle("applicationfolder/toolsfolder/supertoolfolder/supertool.exe"
> plugins libs)
> fixup_bundle("applicationfolder/toolsfolder/toptoolfolder/toptool.exe"
> plugins libs)
> fixup_bundle("applicationfolder/main.exe" plugins libs)
>
>
> --
> Benjamin BALLET
> Ingénieur R
>
> ACTIVISU
> 19, rue Klock - 92110 Clichy
>> Standard Tél :  01 44 69 37 37
>> www.activisu.com
>
> --
>
> 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] fixup_bundle on Windows : issue with multiple exe applications

2016-03-03 Thread Benjamin Ballet 
Hello

I'd like to discuss a problem I encountered today with the very useful
module BundleUtilities

We have an application on Windows with one main exe file in the top folder
and a few other exe in subdirectories, like that :

applicationfolder  \
  | main.exe
  | toolsfolder \
| supertoolfolder \
|
supertool.exe
| toptoolfolder \
 |
toptool.exe

But if I simply call
fixup_bundle("applicationfolder/main.exe" plugins libs)

the verify_app will fails.

Just a reminder that there is no rpath on Windows : dll must be either in
PATH or in the same folder or in the working directory.

We expected fixup_bundle to copy the required dll for main.exe in
applicationfolder, the required dll for supertool.exe in supertoolfolder
and  the required dll for toptool.exe in toptoolfolder, but it acually
didn't copied anything in supertoolfolder and toptoolfolder.

I worked around this issue by calling fixup_bundle multiple time with the
following order : (the deepest exes first)

fixup_bundle("applicationfolder/toolsfolder/supertoolfolder/supertool.exe"
plugins libs)
fixup_bundle("applicationfolder/toolsfolder/toptoolfolder/toptool.exe"
plugins libs)
fixup_bundle("applicationfolder/main.exe" plugins libs)


-- 
*Benjamin BALLET*
Ingénieur R

*ACTIVISU*
19, rue Klock - 92110 Clichy
*> Standard Tél* :  01 44 69 37 37
*>* www.activisu.com
-- 

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] confused on default actions in find_path and find_library on Mac

2016-03-03 Thread quanzhao198757 

I want to use libpng.dylib in my project, and there is a libpng(version1.6) 
installed by brew:  $ ll /Users/quanzhao/git-space/homebrew/lib/libpng.dylib  $ 
ll /Users/quanzhao/git-space/homebrew/include/png.hthere is another 
libpng(version 1.4) in Mono.framework on Mac:  $ ll 
/Library/Frameworks/Mono.framework/Libraries/libpng.dylib  $ ll 
/Library/Frameworks/Mono.framework/Headers/png.h
I use the same configuration for find_path and find_library, but cmake found 
v1.6-libpng and v1.4-png.h, so my project ran to error.Here is my testing cmake 
code:find_path(MYPNG_INCLUDE_DIRNAMES"png.h"HINTS
${USER_FIND_DIRS}PATH_SUFFIXES"include""include/png"
NO_CMAKE_ENVIRONMENT_PATHNO_CMAKE_PATH
NO_SYSTEM_ENVIRONMENT_PATH)message(" MYPNG_INCLUDE_DIR: 
${MYPNG_INCLUDE_DIR}")find_library(MYPNG_LIBRARYNAMESpngHINTS   
 ${USER_FIND_DIRS}PATH_SUFFIXES"lib""local/lib"
NO_CMAKE_ENVIRONMENT_PATHNO_CMAKE_PATH
NO_SYSTEM_ENVIRONMENT_PATH)message(" MYPNG_LIBRARY: ${MYPNG_LIBRARY}")
The result and values of some variables are shown as 
following:USER_CMAKE_ARGS:
 -G 'Unix Makefiles' -DUSER_FIND_DIRS='/Users/quanzhao/git-space/homebrew' 
-DCMAKE_TARGET_BUILD_TOOL:STRING='make' -DUSER_TARGET='x86_64-macosx-clang' 
-DCMAKE_BUILD_TYPE:STRING='Debug' -DCMAKE_C_COMPILER='/usr/bin/gcc' 
-DCMAKE_CXX_COMPILER='/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang++'
 
-DUSER_MODULE_SOURCE_DIR='/Users/quanzhao/git-space/tigerknows-mapcore/externals'
 
-DUSER_MODULE_BINARY_DIR='/Users/quanzhao/git-space/tigerknows-mapcore/x86_64-macosx-clang-debug.make.build/modules'
 
-DCMAKE_INSTALL_PREFIX='/Users/quanzhao/git-space/tigerknows-mapcore/x86_64-macosx-clang-debug.make.build/installs'skip(NO_DEFAULT_PATH):
 1. skip(NO_CMAKE_PATH): 1.   test(CMAKE_LIBRARY_ARCHITECTURE): 1. each 
/include/ in CMAKE_PREFIX_PATH: 1.   each /include in 
CMAKE_PREFIX_PATH: 1.   CMAKE_INCLUDE_PATH: 1.   CMAKE_FRAMEWORK_PATH: 2. 
skip(NO_CMAKE_ENVIRONMENT_PATH): 2.   test(CMAKE_LIBRARY_ARCHITECTURE): 2. 
each /include/ in CMAKE_PREFIX_PATH: 2.   each /include 
in CMAKE_PREFIX_PATH: 2.   CMAKE_INCLUDE_PATH: 2.   CMAKE_FRAMEWORK_PATH: 3. 
HINTS4. skip(NO_SYSTEM_ENVIRONMENT_PATH): 4.   PATH: 
/Users/quanzhao/git-space/depot_tools:/Applications/CMake.app/Contents/bin:/Users/quanzhao/packages/apache-maven-3.3.9/bin:/Applications/Cocos/tools/ant/bin:/Users/quanzhao/git-space/homebrew/bin:/Users/quanzhao/packages/android-ndk-r10e:/Users/quanzhao/packages/adt-bundle-mac-x86_64-20140702/sdk:/Applications/Cocos/frameworks:/Users/quanzhao/packages/cocos2d-x-3/templates:/Applications/Cocos/frameworks/cocos2d-x-3.9/tools/cocos2d-console/bin:/Library/Java/JavaVirtualMachines/jdk1.8.0_65.jdk/Contents/Home:/usr/local/bin:/usr/bin:/bin:/user/sbin:/sbin4.
   INCLUDE: 5. skip(NO_CMAKE_SYSTEM_PATH): 5.   
test(CMAKE_LIBRARY_ARCHITECTURE): 5. each /include/ in 
CMAKE_SYSTEM_PREFIX_PATH: 
/usr/local;/usr;/;/Applications/CMake.app/Contents;/Users/quanzhao/git-space/tigerknows-mapcore/x86_64-macosx-clang-debug.make.build/installs;/sw;/opt/local5.
   each /include in CMAKE_SYSTEM_PREFIX_PATH: 
/usr/local;/usr;/;/Applications/CMake.app/Contents;/Users/quanzhao/git-space/tigerknows-mapcore/x86_64-macosx-clang-debug.make.build/installs;/sw;/opt/local5.
   CMAKE_SYSTEM_INCLUDE_PATH: 
/usr/include/w32api;/usr/X11R6/include;/usr/include/X11;/usr/pkg/include;/opt/csw/include;/opt/include;/usr/openwin/include5.
   CMAKE_SYSTEM_FRAMEWORK_PATH: 
~/Library/Frameworks;/Library/Frameworks;/Network/Library/Frameworks;/System/Library/Frameworks6.
 PATHSCMAKE_FIND_FRAMEWORK: FIRSTCMAKE_FIND_APPBUNDLE: 
FIRSTCMAKE_FIND_ROOT_PATH: CMAKE_STAGING_PREFIX: CMAKE_SYSROOT: 
CMAKE_FIND_PATH_MODE_INCLUDE: 
skip(NO_DEFAULT_PATH):
 1. skip(NO_CMAKE_PATH): 1.   test(CMAKE_LIBRARY_ARCHITECTURE): 1. each 
/lib/ in CMAKE_PREFIX_PATH: 1.   each /lib in 
CMAKE_PREFIX_PATH: 1.   CMAKE_LIBRARY_PATH: 1.   CMAKE_FRAMEWORK_PATH: 2. 
skip(NO_CMAKE_ENVIRONMENT_PATH): 2.   test(CMAKE_LIBRARY_ARCHITECTURE): 2. 
each /lib/ in CMAKE_PREFIX_PATH: 2.   each /lib in 
CMAKE_PREFIX_PATH: 2.   CMAKE_LIBRARY_PATH: 2.   CMAKE_FRAMEWORK_PATH: 3. 
HINTS4. skip(NO_SYSTEM_ENVIRONMENT_PATH): 4.   PATH: