On 27.09.2017 17:18, Michael Ellery wrote:
>> On Sep 26, 2017, at 10:39 PM, Yegor Yefremov
>> wrote:
>>
>> I've seen, that CMake has updated UseSWIG in version 3.8.x. But it doesn't
>> seem to support the following use case:
>>
>> swig -c++
I've seen, that CMake has updated UseSWIG in version 3.8.x. But it doesn't seem
to support the following use case:
swig -c++ -javascript -node interface.i src.c
I.e. I can define "-c++" via set_property(SOURCE interface.i PROPERTY CPLUSPLUS
ON), but how to specify "-node" or "-jsc" or "-v8"?
B
I'm trying to construct a suitable toolchain for CMake 3.0.2. I took
Buildroot's toochain.cmake and trying to tweak it:
set(CMAKE_SYSTEM_NAME Linux)
set(CMAKE_SYSTEM_PROCESSOR armv7l)
# specify the cross compiler
SET(CMAKE_C_COMPILER "/usr/bin/arm-linux-gnueabihf-gcc")
SET(CMAKE_CXX_COMPILER "/
>> I'm using CMake, MinGW and Eclipse as described here
>> http://www.cmake.org/Wiki/Eclipse_CDT4_Generator. In my project I
>> need to compile a resource file, so I've used the
>> add_custom_command() to achieve this. If I run make in MSYS it
>> succeeds, but running from Eclipse causes a problem
I'm using CMake, MinGW and Eclipse as described here
http://www.cmake.org/Wiki/Eclipse_CDT4_Generator. In my project I need to
compile a resource file, so I've used the add_custom_command() to achieve this.
If I run make in MSYS it succeeds, but running from Eclipse causes a problem,
since Ecli
> I am working on a CPack/NSIS based installer for MariaDB. The early
> parts were really easy to do, but now it becomes more complicated.
>
> First problem: I have a set of files with the bootstrap MySQL/MariaDB
> database files. Some users might not want to install these, if they are
> installin
I need to install some configuration files to application data directory. I
found following variable in NSIS docs
(http://nsis.sourceforge.net/Docs/Chapter4.html) as $APPDATA:
"The application data directory. Detection of the current user path requires
Internet Explorer 4 and above. Detection o
Hi Droscy,
> Hi, probably you need to escape the backslashes 3 times, because when
> cmake passes the option to cpack, it removes one escape, and cpack does
> the same when creating nsis file. And you can also use single quote mark
> in order to get the quotation on the final nsis file.
>
> So yo
I'm using CPack for NSIS and would like to place my exe file in
$SMPROGRAMS\$STARTMENU_FOLDER and not in $SMPROGRAMS\$STARTMENU_FOLDER\bin. The
only way to do it is using CPACK_NSIS_CREATE_ICONS.
With this expression
set(CPACK_NSIS_CREATE_ICONS "CreateShortCut
\$SMPROGRAMS\\$STARTMENU_FOLDER\\
> I’m trying to cross compile for ARM with this command:
>
>
>
> cmake . -DCMAKE_BUILD_TYPE=DEBUG -DCMAKE_TOOLCHAIN_FILE=arm-gcc3.4.5.cmake
>
>
>
> Here is my toolchain file:
>
>
>
> INCLUDE(CMakeForceCompiler)
>
>
>
> # this one is important
>
> SET(CMAKE_SYSTEM_NAME Linux)
>
> s
Alexander Neundorf wrote:
> On Thursday 28 January 2010, Hendrik Sattler wrote:
>> Zitat von Yegor Yefremov :
>>> are these two statements not doubled?
>>>
>>> +#elif defined(__GNU__) && defined(__ELF__) && defined(__ARMEL__)
>>> +# d
O.K. Here are some lines of my CMakeLists.txt:
set (CMAKE_C_COMPILER arm-linux-gcc)
set (CMAKE_STRIP arm-linux-strip)
>
> Oh, if you do that in CMakeLists.txt this is quite late. You should use a
> toolchain file as described in the wiki.
I'll try it later.
message (ST
Brad King wrote:
> Yegor Yefremov wrote:
>> O.K. Here are some lines of my CMakeLists.txt:
>>
>> set (CMAKE_C_COMPILER arm-linux-gcc)
>> set (CMAKE_STRIP arm-linux-strip)
>> message (STATUS "ABI ${CMAKE_C_COMPILER_ABI}")
>>
>> After ru
Brad King wrote:
> Yegor Yefremov wrote:
>> Alexander Neundorf wrote:
>>> You should then get the variables CMAKE_(C|CXX)_COMPILER_ABI set to
>>> either "ELF ARM" or "ELF ARMEABI".
>> Do I see it right, that this variable is relevant when buil
Alexander Neundorf wrote:
> please apply the attached patch to Modules/CMakeCompilerABI.h (current CVS,
> but 2.8.0 should work too).
Thank you for the patch. I applied it to the 2.8.0.
> You should then get the variables CMAKE_(C|CXX)_COMPILER_ABI set to
> either "ELF ARM" or "ELF ARMEABI".
D
Alexander Neundorf wrote:
> On Friday 22 January 2010, Yegor Yefremov wrote:
>> Hello,
>>
>> I have two toolchains to compile programs for ARM Debian: one supporting
>> older ABI (Etch) and one for EABI (Lenny). How can I determine the ABI
>> version using CMake?
&
Hello,
I have two toolchains to compile programs for ARM Debian: one supporting older
ABI (Etch) and one for EABI (Lenny). How can I determine the ABI version using
CMake?
Thank you in advance.
Best regards,
Yegor
___
Powered by www.kitware.com
Visi
>> Hello,
>>
>> I use gengetopt to generate command line parser for my application. The
>> configuration file *.ggo also specifies programs version like this:
>>
>> # Name of your program
>> package "hwtest" # don't use package if you're using automake
>> # Version of your program
>> version "1.2.
Hello,
I use gengetopt to generate command line parser for my application. The
configuration file *.ggo also specifies programs version like this:
# Name of your program
package "hwtest" # don't use package if you're using automake
# Version of your program
version "1.2.1" # don't use version
_
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Best regards,
Yegor Yefremov
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
Brandon Van Every wrote:
On 7/13/07, Yegor Yefremov <[EMAIL PROTECTED]> wrote:
# executables
add_executable (test ${SRCS})
add_custom_command (TARGET test POST_BUILD COMMAND ctags -R
WORKING_DIRECTORY ${TEST_SOURCE_DIR} COMMENT "Creating tags" VERBATIM)
Does changing the
s been built
It is only said when the command will happen and not where to place
the statement in the CMakeLists.txt. I interpret this as if I define
PRE_LINK or PRE_BUILD then the cmake will evaluate this properly.
It should be also mentioned in the docu
Brandon Van Every wrote:
On 7/13/07, Yegor Yefremov <[EMAIL PROTECTED]> wrote:
Hello,
I want to use ADD_CUSTOM_COMMAND to create tags when building the
project. The first problem, ADD_CUSTOM_COMMAND must be placed after the
target definition. Should it be so?
Yes. And it's reason
e.
But for me it is not the case.
Best regards,
Yegor Yefremov
project (TEST)
# some parameters
set (CMAKE_VERBOSE_MAKEFILE OFF)
# sources
set (SRCS test.c)
add_custom_command (TARGET test POST_BUILD COMMAND ctags -R WORKING_DIRECTORY
${HWTEST_SOURCE_DIR} COMMENT "Creating tags"
t:
main.c
header.h
I create CMakeLists.txt and after "cmake ." call I suddenly have more
extra files than my project itself.
Best regards,
Yegor Yefremov
___
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake
25 matches
Mail list logo
