hugopl / meique Goto Github PK

If I add a library or change the compiler flags of a target it doesn't get re-linked or re-compiled.

timestamp check if much faster, and it the timestamp wasn't changed for sure the md5 also didn't change, so there's no point to calculate it.

Meique needs a API versioning mechanism to protect users from lua API changes.

There's no way to turn off colored output at runtime.

To reproduce:
$ meique benchmark

A solution would be just put the files into another file when the file list is larger than N.

There's no check to detect two or more targets with the same name.

In fact there's no way to tell meique to use C++ unless using project custom flags

There's no reasons to have different names, the method name can be just "use()"

Example:

• project with main.cpp, foo.cpp and foo.h
• main.cpp includes foo.h
• project compiled
• renames foo.h to bar.h and foo.cpp to bar.cpp
• compiles again, meique wont compile main.cpp, probably because some error occur when calculating the hash of a file that doesn't exists.

buildDir() should return relative path instead of absolute.

The configure step isn't needed, we have all information to start building on the first meique call, a configure step only makes sense for meta build system like cmake.

The location should be queried via pkg-config

Fully parallel by default.

e.g.:
in meique.lua

• A executable target with main.cpp and foo.cpp

in lib/meique.lua

• A shared library target with bar.cpp and ../foo.cpp

Meique will use the same build/foo.cpp.o on both target and the link will fail because foo.cpp wasn't compiled with -fPIC or -fpic.

Sometimes you do heavy stuff and store it on a variable, would be nice to not having to do this stuff in every incremental build, the proposed syntax:

cache(variable)

Doing this will store the variable on meiquecache.lua, and it's value will be restored before any meique.lua file get's parsed.

The main problem is find a way to get the variable name inside cache function, there's no preprocessor here :-)

To reproduce:

1. Create a shared library target called foo.
2. Create a static library target called bar that needs to link with foo to work.
3. Create a executable target that only uses bar, the linker will fail because meique forgot to link it with foo (needed by bar).

Uninstall (meique -u) isn't implemented!

A QtCreator plugin for meique would be very nice to have, besides I think it's not hard to do.

_preCompileHooks aren't called.

The current algorithm works, but could be much better, I already have the algorithm in my mind and some paper :-), now is time to implement and maybe blog post about it.

We may have the current way of doing it as fallback, but the best way is delegate it to the compiler as ninja does.

It's important to have one. It should be generated from the documentation.html page.

There's no way to see the user options on meique --help

Meique should look for the location of Qt rcc via pkg-config, e.g.:

pkg-config --variable=rcc_location QtCore