On 06/09/17 22:11, Chris Richardson wrote:
autotools
Unable to believe CMake could possibly be this rubbish (I am a devotee I'm
afraid) I've just spent the last couple of hours sifting through the
CMake's own source code to track this one down. It turns out that you have
collectively conspired
On Wed, 2017-09-06 at 22:11 +0100, Chris Richardson wrote:
> ...
> CMake: 1, distutils: nil.
Thank you, thank you.
I was trying to understand this incoherent behaviour not quite
believing it could exist in cmake.
All-in-all cmake is like democracy (according to Churchill) - "...
democracy is the
autotools
Unable to believe CMake could possibly be this rubbish (I am a devotee I'm
afraid) I've just spent the last couple of hours sifting through the
CMake's own source code to track this one down. It turns out that you have
collectively conspired to besmirch the good name of CMake and an imm
Alan -
Hate cmake? Maybe you'd be interested in automake instead.
/me ducks
;)
On Wed, Sep 6, 2017 at 2:44 PM, Alan Conway wrote:
> On Wed, Sep 6, 2017 at 12:58 PM, Gordon Sim wrote:
>
>> It seems that the install directive for PROGRAMS in cmake somehow
>> evaluates and rewrites the interpre
On Wed, Sep 6, 2017 at 12:58 PM, Gordon Sim wrote:
> It seems that the install directive for PROGRAMS in cmake somehow
> evaluates and rewrites the interpreter directive in some way.
>
> E.g. in dispatch there is:
>
> install(PROGRAMS
>> ${CMAKE_CURRENT_SOURCE_DIR}/tools/qdstat
>> ${CMAKE
It seems that the install directive for PROGRAMS in cmake somehow
evaluates and rewrites the interpreter directive in some way.
E.g. in dispatch there is:
install(PROGRAMS
${CMAKE_CURRENT_SOURCE_DIR}/tools/qdstat
${CMAKE_CURRENT_SOURCE_DIR}/tools/qdmanage
DESTINATION bin)
The fir
Hello,
In one of our tests, we were having a random failure. It seems we cannot stop a
broker correctly.
We have a started broker and we call "bin/qpid.stop $BROKER_PID" to stop it. It
seems to work from the first time but maybe not fast enough because the script
keeps trying to kill the brok
