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
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
_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/
The following issue has been SUBMITTED.
==
https://cmake.org/Bug/view.php?id=16005
==
Reported By:James Tocknell
Assigned To:
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
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
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
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
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
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
>
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
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
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
13 matches
Mail list logo