Never seem to get a cgreen-runner executable about cgreen HOT 5 CLOSED

Do you get any errors, or is the build finishing ok but no cgreen-runner?

If you get the library built, then I think you might have encountered the situation described in the README. To get the cgreen-runner you also need libbfd.

On Ubuntu this should do it

apt install binutils-dev

If not, get back with more details.

(Migrating from nm to libbfd to auto-discover tests introduced automatic "intelligence" to not build the runner if that library was not found. We should probably look into making a bigger warning when that happens, since using the runner is the prefered way to use cgreen.)

from cgreen.

The build finished ok, with no apparant warnings, but no cgreen-runner :-(
Yes I did indeed need binutils-dev (on Alpine), and then it all was fine.
Thanks for the help
I definitely agree that adding some warnings for this situation would be nice.

I had to remove the line make test, leaving just make and make install
as 7 of the tests were failing (again on Alpine).

from cgreen.

Thanks for cyber-dojo! And I'm glad it was nothing more complicated.

from cgreen.

I had to remove the line make test, leaving just make and make install
as 7 of the tests were failing (again on Alpine).

This seems strange. I haven't built on Alpine, but it builds and passes all tests on Ubuntu.

(Although I found that the Makefile invokes ctest with incorrect arguments. It doesn't take a "dir" argument, so should be "cd build; ctest" instead.)

Could you attach the output from the failing tests run with verbose, please? (cd build; ctest -V)

from cgreen.

Ok. I pulled the Alpine Docker image and see the errors:

The following tests FAILED:
      7 - constraint_messsages (BAD_COMMAND)
      8 - custom_constraint_messsages (BAD_COMMAND)
      9 - mock_messsages (BAD_COMMAND)
     10 - failure_messages (Failed)
     11 - assertion_messages (BAD_COMMAND)
     12 - ignore_messages (Failed)
     13 - xml_output (BAD_COMMAND)

Right?

from cgreen.