On 4/22/2016 4:51 AM, Mueller-Roemer, Johannes Sebastian wrote:
It is true that there is no official bundled installer with both, but
the official installer works just fine with mingw as long as you pass in
the correct target to clang(++)
For example
clang++ --target=x86_64-w64-mingw32 test.cpp
On 2016-04-22 14:59-0400 Nick Deubert wrote:
Hey everyone, I am trying to build and link some 32bit binaries on
Ubuntu 15.10 64bit, but no matter what combination of arguments I give
FIND_LIBRARY I cannot get it to use the 32bit libs. I have been
scouring the mailing lists and came up with all t
Hey everyone, I am trying to build and link some 32bit binaries on
Ubuntu 15.10 64bit, but no matter what combination of arguments I give
FIND_LIBRARY I cannot get it to use the 32bit libs. I have been
scouring the mailing lists and came up with all these things to try
but nothing has worked so far
Am Freitag, 22. April 2016, 13:28:33 schrieb Nils Rathmann:
> Hi Alex,
> thanks for the details. I managed to add the header files as intended
> and do have the targets you described, but the virtual directories
> "CMake Rules", "Object Files" and "Ressources" of each Target
> subdirectory are stil
Hi Chao,
You can see this more clearly if you do a "make VERBOSE=1" :
[chuck.atkins@hal9000 build]$ make VERBOSE=1
...
[ 50%] Building C object CMakeFiles/main.dir/main.c.o
/usr/bin/cc -o CMakeFiles/main.dir/main.c.o -c
/home/chuck.atkins/Code/tmp/source/main.c
[100%] Linking C executable m
Hi Alex,
thanks for the details. I managed to add the header files as intended
and do have the targets you described, but the virtual directories
"CMake Rules", "Object Files" and "Ressources" of each Target
subdirectory are still empty. What is the intention of these virtual
directories?
Th
Sorry for i just know reply by email and thinks for your help again. :-)
Petr Kmoch wrote
> No, it is indeed compiled and linked just fine. What I meant is:
>
> Without any custom commands, the build process conceptually looks like
> this:
>
> buildMain() {
> compile_object_files();
> link_
No, it is indeed compiled and linked just fine. What I meant is:
Without any custom commands, the build process conceptually looks like this:
buildMain() {
compile_object_files();
link_main_binary();
message("Built target main");
}
With a post-build custom command:
buildMain() {
compil
It is true that there is no official bundled installer with both, but the
official installer works just fine with mingw as long as you pass in the
correct target to clang(++)
For example
clang++ --target=x86_64-w64-mingw32 test.cpp
However, it assumes that mingw64 is installed under C:/mingw64
Hi,
the reason is that the post-build command is actually a part of building
"main the target." Once you introduce custom commands into a target,
building it includes them all, and not just compiling the object files and
linking the binary. You will notice that the "Linking C exectuable main"
line
On Fri, Apr 22, 2016 at 8:59 AM, Mueller-Roemer, Johannes Sebastian <
johannes.sebastian.mueller-roe...@igd.fraunhofer.de> wrote:
> You are mistaken, Clang absolutely also works with MinGW. Or it did at
> least up to 3.7 (didn’t get around to trying 3.8 yet)
>
>
>
Clang works fine with libstdc++
You are mistaken, Clang absolutely also works with MinGW. Or it did at least up
to 3.7 (didn’t get around to trying 3.8 yet)
From: CMake [mailto:cmake-boun...@cmake.org] On Behalf Of Cristian Adam
Sent: Thursday, April 21, 2016 23:30
To: Johan Holmberg
Cc: cmake@cmake.org
Subject: Re: [CMake] Us
12 matches
Mail list logo
