hi
is mpic++ --showme:compile output supposed to be assigned to
MPI_CXX_COMPILE_FLAGS variable in cmake?
MPI_CXX_FOUND
MPI_CXX_COMPILER
MPI_CXX_INCLUDE_PATH
MPI_CXX_LIBRARIES
are correctly populated but
"${MPI_CXX_COMPILE_FLAGS}"
"${MPI_CXX_LINK_FLAGS}"
are empty.
However
Frndzz..
I am attaching an archive file herewith!!!..In it the ".h" file of project A
is not able to link to the ".h" file of project B when linking the library
of A as well as B with the executable..This is just an outline of what i
want to execute in my project.
I am a beginner to CMake so very
Hi Daniel
On 02/10/2011 15:03, Daniel Dekkers wrote:
With...
SET_TARGET_PROPERTIES( ${APP_NAME} PROPERTIES MACOSX_BUNDLE_INFO_PLIST
${PLIST_TEMPLATE} )
... we set a path to a Info.plist template (we actually got separate ones for iOS and
OSX). Maybe you can call them what you want, haven't t
hello,
as many of us, i am making a library and this is my first time. I have some
concept questions.
for example, my library depends on "GLEW" library. Therefore applications
that use my library must compile with "-lmylib" and "-lGLEW"
is it possible, to make the "-lGLEW" implicit inside my l
On 10/01/2011 10:07 AM, Yuri Timenkov wrote:
> that's the problem: you don't know neither file name nor it's location,
> especially in multi-configuration generators.
You *do* know a debug file's name and location, either because you must
generate it explicitly (objcopy approach) or via the concer
On 10/01/2011 01:35 PM, Rolf Eike Beer wrote:
> Am Samstag 01 Oktober 2011, 06:11:44 schrieb Michael Hertling:
>> On 09/30/2011 08:39 AM, Rolf Eike Beer wrote:
On 09/29/2011 06:15 AM, Yuri Timenkov wrote:
> When I was investigating similar problem, I found alternative
> approach
>
With...
SET_TARGET_PROPERTIES( ${APP_NAME} PROPERTIES MACOSX_BUNDLE_INFO_PLIST
${PLIST_TEMPLATE} )
... we set a path to a Info.plist template (we actually got separate ones for
iOS and OSX). Maybe you can call them what you want, haven't tried.
"Info.plist.in" would be good. I'll try.
These te
Hi Daniel, can you clarify this a bit? Do you have an example?
On 30/09/2011 15:23, Daniel Dekkers wrote:
Correction: not the Info.plist. That is treated differently because CMake
generates its own for the project.
You can set a "template" Info.plist though where ${VARIABLE} entries are
subsit
