I'm not sure if special characters are sorted before or after alpha.

The ordering is like so:

foo
foo-bar
foo-baz
foobar

so what you have here is correct. In any case, you can use the addport.sh script to add a new port, and it will insert entries in the category makefile in the correct
order.

We use the C ordering, so, LANG=C sort. Best would be to use the addport script to add ports, so you do not have to think about these things.

Default, remove.

I think all of those could be simplified with doing:

STATIC_CMAKE_BOOL= BUILD_STATIC

Oops, I get it wrong half the time:

USE_CSTD= c11

Got it, btw why doesn't compiler:c11 set this automagically? I can't see a good reason for requesting a standards and not also enforcing it as the USES does here. What am I missing?

Will fix and verify.

Because they are not the same thing.

• compiler:c11 means I need a compiler that understands c11
• -std=c11 means that the code is written according to the c11 syntax.

You can write C code using, say, the c99 syntax and using some c11 features, and you can write code that uses the c11 syntax and only uses basic features from the k&r times.

That makes sense, I am still learning C, understand the basics but don't know many of the libraries. Don't understand the difference in standards had thought the newer standards just added headers for new functions in the core language. Thanks for explanation.

Most of them are backwards, on is off and off is on so that can't utilize the _bool option helper.

5.13.3.4.2. OPT_CMAKE_BOOL and OPT_CMAKE_BOOL_OFF