Le mar. 23 oct. 2018 à 08:07, Илья Шипицин a écrit :
> Eric, thank you for your review.
> I still wonder why is it so complicated (my expectation was "ok, since I
> use both cmake and cpack, they should work together")
>
The main reason is that CPack was first design as a standalone tool that
ca
Eric, thank you for your review.
I still wonder why is it so complicated (my expectation was "ok, since I
use both cmake and cpack, they should work together")
can you please review
https://github.com/SoftEtherVPN/SoftEtherVPN/commit/139fffe6e0c218f580cd8a397d94856be37fa947
(it is based on your su
Le lun. 22 oct. 2018 à 23:05, Craig Scott a
écrit :
>
>> Yes I agree that having build rpath is useful.
>> I am not aware of any mechanism that enable calling some tool during
>> CPack's install step.
>> Moreover I don't use MacOS at all so I don't have any experience with
>> PackageMaker.
>>
>>
On Tue, Oct 23, 2018 at 12:32 AM Eric Noulard
wrote:
>
>
> Le lun. 22 oct. 2018 à 11:56, Anatoly Belyaev a
> écrit :
>
>> We use "PackageMaker" generator on MacOS. But i don't think it is CPack
>> specific tool does call strip command. The code for RPATH rewrite and
>> strip cmd is located in
Le lun. 22 oct. 2018 à 11:56, Anatoly Belyaev a écrit :
> We use "PackageMaker" generator on MacOS. But i don't think it is CPack
> specific tool does call strip command. The code for RPATH rewrite and
> strip cmd is located in cmake_install.cmake. As i understand CPack calls
> make install to
We use "PackageMaker" generator on MacOS. But i don't think it is CPack
specific tool does call strip command. The code for RPATH rewrite and
strip cmd is located in cmake_install.cmake. As i understand CPack calls
make install to tmp dir and then creates package.
Having different RPATH for
Le 22/10/2018 à 11:19, Marc CHEVRIER a écrit :
Variable must be specified using upper case. So 'set (JAVA_HOME ...)'
should be OK (or environment variable JAVA_HOME is OK as well). javac
is expected to be in $JAVA_HOME/bin.
Yes, It is :
set(JAVA_HOME /usr/lib/jvm/jdk1.6.0_45)
Le lun. 22
Variable must be specified using upper case. So 'set (JAVA_HOME ...)'
should be OK (or environment variable JAVA_HOME is OK as well). javac is
expected to be in $JAVA_HOME/bin.
Le lun. 22 oct. 2018 à 10:16, Stéphane Ancelot a
écrit :
> Hi,
>
> If I set java_home in cmake 3.12 , Java_JAVAC_EXECU
Option INCLUDE_JARS is used to specify classpath javac option for java
sources compilation.
Currently, there is no possibility to add jars using add_jar command. You
have to use a custom command for that purpose.
Le lun. 22 oct. 2018 à 11:05, Stéphane Ancelot a
écrit :
> Hi,
>
> I have to packa
Hi,
I have to package some jar files in the final jar.
I can compile it with add_jar specifying INCLUDE_JARS but unfortunately,
they are not added to the final target jarfile
Regards
S.Ancelot
--
Powered by www.kitware.com
Please keep messages on-topic and check the CMake FAQ at:
http://w
We use CMake
|add_custom_command(TARGET POST_BUILD COMMAND codesign ...) |
for signing executable files on build. It works fine, but when CPack
generates package it rewrites rpath on executable files and call strip
command on them. This changes the file and invalidates the signature. Is
there
Hi,
If I set java_home in cmake 3.12 , Java_JAVAC_EXECUTABLE is not using my
java_home env but /usr/bin/javac
what is wrong ?
Regards,
S.Ancelot
--
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 va
12 matches
Mail list logo
