Re: [CCPPETMR/SIRF-SuperBuild] potential version conflicts with system libraries (#18)

0 views
Skip to first unread message

Kris Thielemans

unread,
May 8, 2017, 7:24:38 PM5/8/17
to CCPPETMR/SIRF-SuperBuild, Subscribed

Robert Maynard at kitware.com suggests

Have you tried using CMAKE_PREFIX_PATH instead of CMAKE_INSTALL_PREFIX?

@paskino, could you give that a try? e.g. remove the BOOST_ROOT variable pass-through, and see if it still picks up our files as opposed to the system ones. please also test for GTest (copy libgtest.a to /usr/local/lib. it should NOT be found, but will be at present)


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Edoardo Pasca

unread,
May 15, 2017, 9:21:28 AM5/15/17
to CCPPETMR/SIRF-SuperBuild, Subscribed

I've tested right now.

  1. Installed system boost
  2. removed -DBOOST_ROOT

it found the system boost. So the BOOST_ROOT variable seems necessary.

Kris Thielemans

unread,
May 15, 2017, 11:30:20 AM5/15/17
to CCPPETMR/SIRF-SuperBuild, Subscribed

did you add CMAKE_PREFIX_PATH in the External_SIRF.cmake ? (or whatever project you tried)

Edoardo Pasca

unread,
May 16, 2017, 5:23:46 AM5/16/17
to CCPPETMR/SIRF-SuperBuild, Subscribed

I tried it on Gadgetron. The CMAKE_PREFIX_PATH was already there.

Kris Thielemans

unread,
May 16, 2017, 9:21:37 AM5/16/17
to CCPPETMR/SIRF-SuperBuild, Subscribed

ah well. indeed, this was already there when we tried with David. I'll reply to the CMake list.

Kris Thielemans

unread,
Aug 11, 2018, 5:19:56 PM8/11/18
to CCPPETMR/SIRF-SuperBuild, Subscribed

Closed #18.

Kris Thielemans

unread,
Aug 11, 2018, 5:19:56 PM8/11/18
to CCPPETMR/SIRF-SuperBuild, Subscribed

Closing this as probably resolved. However, see also related #129

Reply all
Reply to author
Forward
0 new messages