| 1 |
On Sunday, June 06, 2010 03:45:51 Michał Górny wrote: |
| 2 |
> On Sun, 6 Jun 2010 00:17:27 -0400 Mike Frysinger wrote: |
| 3 |
> > i'm not saying `emake` covers all solutions you proposed, just that |
| 4 |
> > the base usage isnt nearly as bleak. there are some cases where |
| 5 |
> > having a wrapper around emake would be useful (such as compiling |
| 6 |
> > multiple files or linking things in). so if you wanted to slap |
| 7 |
> > something together, we can look at it further. |
| 8 |
> |
| 9 |
> Well, I've already covered one corner case myself, which is the zpaq |
| 10 |
> ebuild. I would approve a comment on my idea here: |
| 11 |
> |
| 12 |
> http://overlays.gentoo.org/proj/sunrise/changeset/10641/sunrise/app-arch/zp |
| 13 |
> aq/zpaq-1.10.ebuild |
| 14 |
> |
| 15 |
> The hard part was that zpaq.cpp had to be compiled to both the execu- |
| 16 |
> table and the stub object file (with additional -DOPT flag). |
| 17 |
> |
| 18 |
> I've decided that the simplest and most fail-proof idea was to create |
| 19 |
> an additional source file, defining 'OPT' and including the real code, |
| 20 |
> and compiling all of that within a single 'emake' call. |
| 21 |
|
| 22 |
C/C++ files should always have a newline at the end ... that stub file is |
| 23 |
currently missing one. |
| 24 |
|
| 25 |
i dont know anything about zpaq, but it looks like you're installing the bare |
| 26 |
.o files ? that's a bit odd. usually things like this are installed as |
| 27 |
static archives for people to link in ... |
| 28 |
|
| 29 |
wrt the emake stuff, that looks fine |
| 30 |
-mike |
Archives