Hi,

strange: using x.inl works as long as the x.inl path is
absolute
SET( x_MY_DIR ${base_DIR}/x )
SET( x_SRC
 ${x_MY_DIR}/x.inl
)

using a relative path:
SET( x_MY_DIR ${x_SOURCE_DIR}/../x )
SET( x_SRC
 ${x_MY_DIR}/x.inl
)
the visual studio tries to compile x.inl!

but if I use absoulte paths (first example), having
multiple object files with the same name doesn't work...

Shall I file a bug report for this

Cheers,
Manuel




> Hi,
>
> An easy way out would be to rename all x_inc.cpp to x.inl. Usually inl
> files are ignored by the VS compiler (they're marked as headers), and
> you have a better way to distinguish between generated and "real" CPPs.
>
>
> Cheers,
> Laurentiu
>
> At 06:44 AM 5/17/2006, Manuel Klimek wrote:
>>Hi there,
>>
>>I've got a problem with SOURCE_GROUPS with cmake 2.4.1 in windows (VC
> 2005).
>>I already found out that if I want to add headers in a source
>>group I'll have to add the headers to the ADD_LIBRARY or
> ADD_EXECUTABLE.
>>But I have the problem that I include platform specific .cpp files
>>in another .cpp file and I want to add those files to the source
> list.
>>I don't know how I can make them show up in the source group without
>>compiling the file:
>># x.cpp includes x_inc.cpp
>>SET( x_SRC x.cpp )
>>SET( x_HDR x.h )
>>SET( x_INC x_inc.cpp )
>>SOURCE_GROUP( "X Sources" ${x_SRC} ${x_INC} )
>>SOURCE_GROUP( "X Headers" ${x_HDR} )
>>ADD_LIBRARY( x STATIC ${x_SRC} ${x_HDR} ${x_INC} )
>>
>
>
> --
> Laurentiu Nicolae
> Senior Software Engineer
> Quintiq
>
> Tel: +31 (0)73 691 07 39
> Fax: +31 (0)73 691 07 54
> [EMAIL PROTECTED]
> www.quintiq.com
>
> ------------------------------------------------------------------------------------------
> This message contains information that may be privileged or
> confidential and is the property of Quintiq. It is only intended for the
> person to whom it is addressed. If you are not the intended recipient,
> you are not authorized to read, print, retain, copy disseminate,
> distribute or use this message or any part thereof. If you receive this
> message in error, please notify the sender immediately and delete all
> copies of this message. Please note that e-mails are susceptible to
> change.
> _______________________________________________
> CMake mailing list
> CMake@cmake.org
> http://www.cmake.org/mailman/listinfo/cmake
>
>
>

_______________________________________________
CMake mailing list
CMake@cmake.org
http://www.cmake.org/mailman/listinfo/cmake

Reply via email to