[Omake] Announcing OMake 0.9.8
Michael Vanier
mvanier at cs.caltech.edu
Tue Dec 12 00:24:53 PST 2006
Hmm. When I do that, I get this:
[tap] omake --verbose clean
*** omake: reading OMakefiles
*** omake: finished reading OMakefiles (0.0 sec)
- build main <clean>
+ Shell.rm(-f main/*.opt main/*.run main/*.o main/*.obj main/*.lib main/*.cm*
main/*.a main/*~ bs)
- exit main <clean>, code 0
- build builtin <clean>
+ Shell.rm(-f builtin/*.opt builtin/*.run builtin/*.o builtin/*.obj
builtin/*.lib builtin/*.cm* builtin/*.a builtin/*~)
- exit builtin <clean>, code 0
- build util <clean>
+ Shell.rm(-f util/*.opt util/*.run util/*.o util/*.obj util/*.lib util/*.cm*
util/*.a util/*~)
- exit util <clean>, code 0
- build base <clean>
+ Shell.rm(-f base/*.opt base/*.run base/*.o base/*.obj base/*.lib base/*.cm*
base/*.a base/*~ lexer.ml parser.ml)
- exit base <clean>, code 0
*** omake: done (0.0 sec, 0/0 scans, 4/4 rules, 0/48 digests)
This would seem to indicate that omake knows what files are supposed to be
removed. But none of the files actually get removed.
Mike
Aleksey Nogin wrote:
> On 11.12.2006 22:03, Michael Vanier wrote:
>
>> Hmm, I compiled and installed omake 0.9.8 and now my "omake clean"
>> target doesn't work properly. It doesn't give any error, it just
>> doesn't clean out the files it used to -- only the final executable, or
>> more specifically the symlink to the final executable (the executable
>> itself is untouched). Any ideas why this might be happening? My
>> OMakefiles are very simple.
>
> Have you tried running "omake --verbose" to see more detail on what is
> going on? Note that OMake now runs with the -S option enabled by
> default, so you might not see as much output.
>
> Aleksey
> _______________________________________________
> Omake mailing list
> Omake at metaprl.org
> https://lists.metaprl.org/mailman/listinfo/omake
More information about the Omake
mailing list