The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13843
==
Reported By:jgu
Assigned To:
The following issue has been SUBMITTED.
==
http://public.kitware.com/Bug/view.php?id=13844
==
Reported By:Ingmar Voigt
Assigned To:
Is a license text file pointed to by CPACK_RESOURCE_FILE_LICENSE
expected to have a specific encoding (ASCII, Latin1, UTF-8, ...)?
Nils
--
Nils Gladitz, B.Sc.
DICOM, Konnektivität und Entwicklung
Scivis wissenschaftliche Bildverarbeitung GmbH
Bertha-von-Suttner-Str. 5
D-37085 Göttingen
2013/1/10 Nils Gladitz glad...@sci-vis.de:
Is a license text file pointed to by CPACK_RESOURCE_FILE_LICENSE expected to
have a specific encoding (ASCII, Latin1, UTF-8, ...)?
I don't know but I bet that some encoding may be accepted by some
CPack generator
and poorly handled by others.
I wrote the WiX part and am pondering how to support extended character
sets without having to provide an extra RTF file.
We've got an english license text file but our company address still
contains a german umlaut.
I could provide an RTF but I'd prefer not to have two license files.
Nils
Steve,
While reviewing this topic I ran the ExportImport test to look for
generator expressions in a link interface property. I do not see
any. The test C++ code appears to verify that libraries are linked
but it is compiled into a static library as added by this commit:
Eike,
On 01/09/2013 11:02 AM, Dave Abrahams wrote:
http://www.cmake.org/Bug/view.php?id=13842
==
We could use C++11 feature detection per http://pageant.ghulbus.eu/?p=664
This picks up from the C++0x patch you posted here:
Am 10.01.2013 16:40, schrieb Brad King:
Eike,
On 01/09/2013 11:02 AM, Dave Abrahams wrote:
http://www.cmake.org/Bug/view.php?id=13842
==
We could use C++11 feature detection per
http://pageant.ghulbus.eu/?p=664
This picks
2013/1/10 Nils Gladitz glad...@sci-vis.de:
I wrote the WiX part and am pondering how to support extended character sets
without having to provide an extra RTF file.
Sorry I did not connect the dots.
We've got an english license text file but our company address still
contains a german
Brad King wrote:
Steve,
While reviewing this topic I ran the ExportImport test to look for
generator expressions in a link interface property. I do not see
any. The test C++ code appears to verify that libraries are linked
but it is compiled into a static library as added by this commit:
Stephen Kelly wrote:
so it seems that the libraries are being passed to the linker, but the
symbols are not being resolved? I haven't yet seen why that is. Any ideas?
The problem was that I was creating a CXX executable without using extern
C. I've pushed a branch to fix it, but haven't
On 01/10/2013 11:17 AM, Stephen Kelly wrote:
The problem was that I was creating a CXX executable without using extern
C. I've pushed a branch to fix it, but haven't merged it to next yet. Will
I do so?
Yes, please. Then rebase the link interface topic on it so the test covers
what we
Brad King wrote:
On 01/10/2013 11:17 AM, Stephen Kelly wrote:
The problem was that I was creating a CXX executable without using extern
C. I've pushed a branch to fix it, but haven't merged it to next yet.
Will I do so?
Yes, please. Then rebase the link interface topic on it so the test
I would prefer a more compicated variadic template test that exercises
variadic code such as:
templatetypename G = void, typename H = void
struct foo
{};
templatetypename... G
struct bar : fooG...
{};
int main() {
barint, float f;
}
So that we detect compilers like gcc 4.6 that supported
Now that the INTERFACE_PIC branch is in, the next topic I have in that line
is the compatible-INTERFACE-user-properties topic I've just pushed to
gitorious.
Because I'll be automatically linking the Qt4::qtmain library into
executables which are WIN32_EXECUTABLEs, and because QtActiveX
On 01/10/2013 01:04 PM, Stephen Kelly wrote:
the COMPATIBLE_INTERFACE_BOOL property:
set_property(TARGET Qt4::QAxServer APPEND PROPERTY
COMPATIBLE_INTERFACE_BOOL QT4_NO_LINK_QTMAIN)
A better name may be INTERFACE_COMPATIBLE_BOOL since the compatibility
requirement is actually part of
Yes, I think I'd prefer UTF-8 as well.
Unless most of the other generators use something else or there is a
contradicting convention or preference for CMake/CPack?
I guess I'll try running some license files through some of the
generators that you listed and see what comes out.
Thank you
The following issue has been SUBMITTED.
==
http://www.cmake.org/Bug/view.php?id=13845
==
Reported By:rbmj
Assigned To:
Brad King wrote:
On 01/10/2013 01:04 PM, Stephen Kelly wrote:
the COMPATIBLE_INTERFACE_BOOL property:
set_property(TARGET Qt4::QAxServer APPEND PROPERTY
COMPATIBLE_INTERFACE_BOOL QT4_NO_LINK_QTMAIN)
A better name may be INTERFACE_COMPATIBLE_BOOL since the compatibility
2013/1/7 Willy Lambert lambert.wi...@gmail.com:
really sorry, last mail was sent too early X-(
2013/1/7 Willy Lambert lambert.wi...@gmail.com:
2013/1/4 Andreas Mohr a...@lisas.de:
Hi,
On Fri, Jan 04, 2013 at 11:47:40AM -0500, cmake-requ...@cmake.org wrote:
Date: Fri, 4 Jan 2013 16:58:05
Hi,
We have the same problem here with ctest and clang on Mac OS X.
Versions used are :
- clang 4.2, from XCode 4.6DP4 on Mac OS X 10.7
- cmake 2.8.10.2
In our ctest script, compilation is launched with 4 jobs (make -j4).
In our dashboard (and same thing when directly looking at the text output
Hello,
When I try to execute cmake on the terminal on windows, I get an error. (See
attachment).
It seems that some variables arent set.
Are there environmental variables or variables set in a specific file.
Thanks a lot your support
Happy new year.
Best regards
My compilretr is minGW.
De : Parchet Michaël [mailto:mparc...@sunrise.ch]
Envoyé : jeudi 10 janvier 2013 21:36
À : cmake@cmake.org; 'KDE on Windows'
Objet : How to set the cmake variable on windows
Hello,
When I try to execute cmake on the terminal on windows, I get an error. (See
I just put up a blog about parallel builds with CMake, that might be of
interest to folks on the list:
http://www.kitware.com/blog/home/post/434
-Bill
--
Powered by www.kitware.com
Visit other Kitware open-source projects at
http://www.kitware.com/opensource/opensource.html
Please keep
Good read.
The only suggestion I would make is for Unix Makefiles, rather than running
'make -jN' is to run 'make -j -lN' which tells make to use as many cores until
the load is greater than N.
This is nice because if I have a 12 core system, I can do 'make -j -l12' and it
will build using 12
Hello,
How can I set minGW as default cmake compiler on windows ?
Tanks for your answer.
Regards
mparchet
Le 10 janv. 2013 à 22:47, Patrick von Reth patrick.vonr...@gmail.com a écrit :
Hi you have to use cmake -GMinGW Makefiles ...
On 10/01/2013, Parchet Michaël mparc...@sunrise.ch wrote:
I am using SWIG with #include directives in the interface file. When I
compile the project for the first time everything works fine, but when
I make modifications to the header file included by the interface file
the generated cxx wrapper file is not re-generated. But the generated
cxx
Hello,
I just had this happening with CMake 2.8.10 ( from a recent macports ) and
with XCode 4.5.2.
I built the step1 tutorial in its source dir :
bash-3.2$ cmake -G XCode .^M
-- The C compiler identification is Clang 4.1.0^M
-- The CXX compiler identification is Clang 4.1.0^M
-- Check for
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, next has been updated
via d890530f055f6ff8a407f86d80ff302c1c93263d (commit)
via
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, next has been updated
via 6d87665bdd2e759b41baf140b4417fe7dfd2237c (commit)
via
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, next has been updated
via d1e5720991480016ae2ff0aaff14e2653199fbd7 (commit)
via
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 8a7a4c043c2fede043ce8bf8676a95e1b779fe5e (commit)
via
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 42d9df9f4f5b06de0f75859cc40750c9b8eec9a1 (commit)
via
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 feb9ffb6815b4367634a1543f42f50ae2f3c4c98 (commit)
via
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 325e92fa22cb20a3d4bccbf1f663c28b34f8b04c (commit)
via
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, next has been updated
via 66f05a4a4b061058ecd41bff01950b168b997e3a (commit)
via
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, next has been updated
via 3741269ac53dfa42b5106a506504fae1d2887679 (commit)
via
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, next has been updated
via 5dcfc38994547a5cee5d8c699a73c6aecb79877b (commit)
via
38 matches
Mail list logo
