codeinred / chroma Goto Github PK

Targets as currently planned: There will be three kinds of targets.

• Object File Targets
• Library Targets
• Executable Targets

Both Executable Targets and Library targets get decomposed into a list of object file targets, and then the command to link everything.

Object file targets consist of an individual .c or .cpp file (other extensions permitted) that gets compiled into an object

Idea: if a library or executable consists of only a single source file (aka c or cpp file), there will be no intermediary step to create an object file

Right now, Chroma uses the current working directory as the start point for it's search. Users should be able to specify the start point with an option on the command line, like so:

chroma build --path /path/to/project

i.e., as a drop-in replacement for Make

Quoted from @codeinred:

If there’s no chroma.toml in the current directory, it should search through parent directories searching for a chroma.toml, and once it finds one, changes the working directory to that directory. This should be done on startup

g++ throws this error when I try to run the hello-chroma example:

g++: error: unrecognized command line option ‘-std=c++20’; did you mean ‘-std=c++2a’

apt indicates that I have the latest version of g++ installed.