| 1 |
Last week I finally got my ebuild generator to generate an ebuild for the |
| 2 |
"moc" music on console project: http://moc.daper.net |
| 3 |
It manages to create an working ebuild with all user configure options |
| 4 |
(useflags) and most of the requiered deps. |
| 5 |
I also found a way to ask gcc for the default include paths. |
| 6 |
They are different in c and c++ projects. I'm not sure how I would detect |
| 7 |
which one of them to use. Now i default to the C include paths. |
| 8 |
|
| 9 |
This week I will spent most of my time to solve the last dependecy problems |
| 10 |
and iron out other problems I run into. |
| 11 |
|
| 12 |
First I need to implement some of the automake (undocumented) automagicly |
| 13 |
generated include flags. Thanks again rafaelmartins (on IRC) for helping me |
| 14 |
figure out this! |
| 15 |
Right now it pulls in one bogus dep for the moc project because of this. |
| 16 |
|
| 17 |
Then I need to do some more work on "ifdef" includes so I handle that |
| 18 |
correctly. But I think that will go quite fast as most of the stuff is |
| 19 |
already in place I just need to rewrite some stuff. |
| 20 |
|
| 21 |
After this I think I'll need to figure out what to do when I can't get the |
| 22 |
correct include paths because there are perhaps generated with pkg-config or |
| 23 |
something like that. |
| 24 |
|
| 25 |
I've also rushed some other parts of the generator. So there are other areas |
| 26 |
that will/might need some improvement. But it seems to work quite nicely |
| 27 |
with the moc project atleast. |
| 28 |
I have focused on that project as it seems to "exploit" quite a few of |
| 29 |
automake/autoconf features so I think if I have it working nicely on that |
| 30 |
one it will work one other autotool projects also. Or atleast there won't be |
| 31 |
much work to implement missing stuff. |
Archives