cjdb / project_template Goto Github PK

Describe the enhancement

cmake/basic_project-add-targets-impl.cmake uses quite a few generator expressions. It would be nice if there was more intrinsic documentation to help maintainers grok what's going on there.

I have done the default setup as per the project README

I couldn't pass the second test
2 - test.demo.employee (Failed)

Entire shell output can be found here:
https://pastebin.com/KkXDVEGM

A quick google search points me to the following answer:
https://stackoverflow.com/questions/39865367/warning-section-textcoal-nt-is-deprecate-since-updating-to-mac-osx-sierra

I was wondering if there is a work around? or Is it safe to ignore these warnings?

Is your feature request related to a problem? Please describe.

Fraud detection mechanism of Cirrus CI is triggering on this repo. It thinks you mine some crypto coins. 😅

Describe the solution you'd like

Two possible things come to mind:

1. Combine some of the tasks if possible to reduce overall CPU footprint of a single change. Two matrixes which results in 38 tasks with 4 cores for each change.
2. Maybe run only a few configurations for PRs and all for master branch? Do you really need both Release and Debug?

/cc @cjdb

Running Mac Sierra
Just installed it per instructions using g++-4.9 (Homebrew GCC 4.9.4)
made build/debug then ran
make && make test
pastebin of error log: https://pastebin.com/2Dvi0dFn
Also when compiling get a whole bunch of errors like this
/var/folders/k2/8stwhnf16hl5srvm31cdkmqw0000gn/T//cc7iHLxz.s:7278:11: note: change section name to "__data" .section __DATA,__datacoal_nt,coalesced ^ ~~~~~~~~~~~~~
But google says they are harmless and unavoidable

Describe the bug

Not all platforms have a Clang system. Requiring Clang should only be required if an LLVM project uses it.

Acceptance criteria

Have a check for any LLVM project before this call to find_package.

Is your feature request related to a problem? Please describe.

Concern has been expressed that only *.hpp files from include/ are installed. Some projects might use *.h, *.hxx, or *.hh. Please consider these as well.

Describe the solution you'd like

Support *.h, *.hxx, and *.hh.

Describe alternatives you've considered

There are no reasonable alternatives.