Hi
My guess is that it's this
ExternalProject_Add_Empty(${proj} DEPENDS "${${proj}_DEPENDENCIES}")
I guess it's needed to be able to have it as a dependency in the other ones, but it just creates empty stuff. Presumably specify SOURCE_DIR etc there as well would solve this (although a bit ridiculous)
kris
-----Original Message-----
From: CCP-PETMR Developers list [mailto:[log in to unmask]] On Behalf Of Edoardo Pasca
Sent: 07 February 2018 17:12
To: [log in to unmask]
Subject: SuperBuild consistent build directory tree
Hi all,
I found how to address https://github.com/CCPPETMR/SIRF-SuperBuild/issues/16 and make the build directory structured as proposed.
However, I still see the following:
1) if we build the package, say FFTW3, then its directory fits the structure: the download goes in Source/FFTW3 the buidl in Build/FFTW3 etc. And I'm happy.
2) if we USE_SYSTEM_FFTW3=0n then 2 directories get created in the build directory: FFTW3 and FFTW3-build. And I'm not happy.
When and why do these directory get created?
Any clue?
Edo
--
Edoardo Pasca, PhD
Visual Analytics and Imaging Systems Group Scientific Computing Department, STFC Rutherford Appleton Laboratoty
0044 (0)1235 44 5660
:wq
|