Hey all,
I recently downloaded MinGW GCC 4.4 and have been toying around with it. I've
been trying to get the shared libstdc++ support working under CMake 2.6.3.
Anyone ever tried this before? Currently I'm having two issues - multiply
defined symbols coming from libstdc++.a and libstdc++_s.
On Jul 6, 2009, at 11:54 AM, James C. Sutherland wrote:
execute_command(
COMMAND ${test_cmd}
COMMAND ${CMAKE_COMMAND} -E compare_files ${output_blessed} $
{output_test}
RESULT_VARIABLE test_not_successful
OUTPUT_QUIET
ERROR_QUIET
)
if( test_not_successful )
message( SEND_ERROR "${output_tes
On Monday 06 July 2009, Nick Davidson wrote:
> Dear List,
>
> Is there an idomatic way of converting an implicit makefile rule to a
> CMakeLists construct?
> Currently I'm resorting to writing a macro which processes list
> variables with foreach and adds various linked custom targets but I'm
> fin
Does CMake support in some form Visual Studio custom build rule files as
opposed to using add_custom_command that makes use of the Custom Build Tool
(VSCustomBuildTool)?
I've had some problems with Visual Studio and generating object files
(Visual Studio bugs), and I was wondering what other optio
On Monday 06 July 2009, alexandre.feb...@thomsonreuters.com wrote:
> Hi,
>
> I need to export() some libraries, but I need to have the part
>
> ADD_LIBRARY( STATIC IMPORTED)
>
> and the part
>
> SET_PROPERTY(TARGET APPEND PROPERTY IMPORTED_CONFIGURATIONS
> RELEASE)
>
> SET_TARGET_PROPERTIE
On Mon, Jul 06, 2009 at 06:07:11PM +0100, Nick Davidson wrote:
> macro (MakeCustomTarget TARGET_FILE CPP XML)
> add_custom_target(TARGET_FILE ALL
> COMMAND process ${TARGET_FILE} ${CPP}
> COMMAND process ${TARGET_FILE} ${XML})
> message(STATUS "Cannot find xgettext")
>
On Mon, Jul 06, 2009 at 05:37:51PM +0200, Karol Krizka wrote:
> Just a quick, side, off-topic question. Does Windows support symlinks?
Short answer: no.
Longer answer: sorta, but not in any meaningful or useful way.
tyler
___
Powered by www.kitware.com
execute_command(
COMMAND ${test_cmd}
COMMAND ${CMAKE_COMMAND} -E compare_files ${output_blessed} $
{output_test}
RESULT_VARIABLE test_not_successful
OUTPUT_QUIET
ERROR_QUIET
)
if( test_not_successful )
message( SEND_ERROR "${output_test} does not match $
{output_blessed}!" )
endif( te
Dear List,
Is there an idomatic way of converting an implicit makefile rule to a
CMakeLists construct?
Currently I'm resorting to writing a macro which processes list
variables with foreach and adds various linked custom targets but I'm
finding lots of confusion when passing lists as arguments to
Hi,
Thank you both for you suggestions. I think I will go with
execute_process and symlinks. Since the files are movies, they are quite
big and links are thus more efficient.
Just a quick, side, off-topic question. Does Windows support symlinks?
--
Cheers,
Karol Krizka
On Sun, 2009-07-05 at 20:2
On Mon, Jul 6, 2009 at 5:36 PM, David Cole wrote:
> This is incorrect.
> CPack only delegates to another installed tool to generate ZIP files. It
> does not know how to write ZIP files itself. The same is true for most CPack
> -G generators: it orchestrates calling an external tool to generate the
This is incorrect.
CPack only delegates to another installed tool to generate ZIP files. It
does not know how to write ZIP files itself. The same is true for most CPack
-G generators: it orchestrates calling an external tool to generate the
actual package created.
Mathieu, the original question w
Well technically you do not need anything extra for ZIP. The only
missing part IMHO is the API from within CPack (cpack is almost always
guarantee to be installed on system providing cmake), see my post:
http://www.cmake.org/pipermail/cmake/2009-January/026361.html
I have not been able to find ou
Thank you - this was a very useful explanation!
For any others who may look at this, note that
execute_command
should be
execute_process
On Jul 4, 2009, at 1:11 AM, Michael Wild wrote:
On 4. Jul, 2009, at 0:56, James C. Sutherland wrote:
I have a test that produces output fi
You're welcome!
Sorry, must have mixed "execute_process" and "custom_command"
together...
Michael
On 6. Jul, 2009, at 16:27, James C. Sutherland wrote:
Thank you - this was a very useful explanation!
For any others who may look at this, note that
execute_command
should be
Hi,
I need to export() some libraries, but I need to have the part
ADD_LIBRARY( STATIC IMPORTED)
and the part
SET_PROPERTY(TARGET APPEND PROPERTY IMPORTED_CONFIGURATIONS
RELEASE)
SET_TARGET_PROPERTIES( PROPERTIES
IMPORTED_LINK_INTERFACE_LIBRARIES_RELEASE ";"
That depends on when you want to run the extraction. At CMake-time or
build-time? If the former, you can use:
execute_process(
COMMAND ${CMAKE_COMMAND} -E tar xzf path/to/file.tar.gz
WORKING_DIRECTORY ${CMAKE_BINARY_DIR}/path/to/where/you/want/to/unpack
)
There are many more options for the ex
I could probably live with .gz files.
What would I have to type inside the CMakeLists.txt file to expand the
archive?
Am 03.07.2009 20:07, schrieb David Cole:
cmake -E tar
can untar .tar files and .tar.gz files... But you have to use an
external tool for .zip files.
We are considering addi
> t...@unforbidable.com wrote:
> >> t...@unforbidable.com wrote:
> >>> So I tried to set EXECUTABLE_OUTPUT_PATH to the same
> >>> path as PROJECT_BINARY_DIR like so:
> >>>
> >>> SET(EXECUTABLE_OUTPUT_PATH "${PROJECT_BINARY_DIR}"
> CACHE >>> PATH "Single output directory for building all
> >>> execu
Zitat von du...@identicalsoftware.com:
Quoting "Hendrik Sattler" :
Am Sonntag 05 Juli 2009 19:36:44 schrieb du...@identicalsoftware.com:
mingw32-SDL is installed. Looking at the FindSDL.cmake and the
CMAKE_FIND_ROOT_PATH directory I can see why it doesn't find it. The
/usr/i686-pc-mingw32 d
OK, I see, thanks.
I was a bit confused, cause I think this is one of the few macros that
really needs a quoted list as argument to function properly. Unless I'm
mistaken, I think most other macro solve this "problem" by either
interchanging the result and input variables, or by using the input
ar
21 matches
Mail list logo