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
19 matches
Mail list logo
