Open MariadeAnton opened 9 years ago
Adding @toeb to the conversation ;)
Boost block uses cmakepp async features to build each requested boost lib in a separate process. The Starting lib build job...
logs is the script forking a process for each build. Then a callback is called from that forked processes during build process (That's the progress bar that comes later).
@toeb implemented that features using OS specific shell scripting, powershell in case of windows. Maybe there's a subtle bug on the windows scripts, but I'm confident there's not. boost/install
block uses my own track of cmakepp block that has been tested on all platforms. Relying on a custom track instead of the main cmakepp one was intended to have a frozen (no let it gooooo please...) version widely tested that does not break Boost builds on each cmakepp release.
I'm booting windows to check the Boost examples again. Please stay tuned.
Hi,
Thank you for your responsiveness and for your team's commitment.
I'll try the boost example on my Windows computer too.
BTW, I use both MinGW and VS2013 compiler to compile/test my projects on Windows.
And I use CLion IDE on all platforms : Windows, Linux and Mac (the issue occurs only on Windows)
clion on windows? We are having issues with clion + boost + windows related to the way the script works. I'm working on it. https://github.com/biicode/boost/issues/10
EDIT: But looking at the behavior of your error, it's not directly related to 10.
Well, that might explain it, then. I'll switch back to Visual Studio on Windows until then.
Thanks again to the biicode team. Keep up the good work!
Hi! Just for others running into the same issue: I am using the msysGit console as a replacement for cmd. All bii commands work fine. However, as soon as I use the boost wrapper, it gets stuck. Switching to cmd fixed it for me.
Any ideas?
I asked for more info just in case.