Hi Brian,
ExternalProject_Add has a DEPENDS option. What you can do is let X
depend on Y and use the CMAKE_CACHE_ARGS option to provide the include
path, or use the buildsystem in project X to find the headers itself.
Regards,
Micha
On 03/19/2014 03:11 AM, Brian Lewis wrote:
> If X brings in Y a
If X brings in Y as an external project, and Y brings in Z as an
external project, is there some way for Y to communicate information
about Z back to X, e.g., some include directory?
My situation is, X doesn't know anything about Z, but needs to be able
to find one of Z's headers. I wish I could a
Can't vouch for 2.15. Are you able to use NSIS 2.46? This works for me
using CMake 2.8.12.2 (I also used a number of previous 2.8 versions
though can't be sure which ones).
On 19/03/14 12:37, Iosif Neitzke wrote:
> When trying to run CPack with NSIS 2.15, i get:
>
> CPack error : Problem checking
When trying to run CPack with NSIS 2.15, i get:
CPack error : Problem checking NSIS version with command:
"C:/NSIS/makensis.exe" /VERSION
Please check ./NSISOutput.log for errors
CPack error : Cannot initialize the generator NSIS
NSISOutput.log:
# Run command: "C:/NSIS/makensis.exe" /VERSION
#
Checked Linux (Ubuntu 12.04).
2.8.12.2 works, so I'm guessing this is a Windows platform issue.
On 18/03/14 16:24, Bruce Cartland wrote:
> I'm upgrading my build from 2.8.8 to the latest toolset.
>
> At this stage I've only tried on Windows 2008 Server R2 Standard SP1 and
> Windows Server 2003 R2
And I did it.
It wasn't populating *MPI_C_INCLUDE_PATH *instead it populated
*MPI_INCLUDE_PATH.*
So now I am using only *MPI_INCLUDE_PATH, MPI_COMPILE_FLAGS, MPI_LINK_FLAGS
and MPI_LIBRARIES *not
* MPI_C_* *
Thanks
Bibrak Qamar
On Tue, Mar 18, 2014 at 11:38 AM, Bruce Cartland
wrote:
> By qu
