[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: .ALIAS builtin pseudotarget
From: |
Boris Kolpackov |
Subject: |
Re: RFC: .ALIAS builtin pseudotarget |
Date: |
Thu, 23 Sep 2004 11:46:48 -0500 |
User-agent: |
Mutt/1.5.6i |
Fabio Alemagna <address@hidden> writes:
> Well, obviously if I do use it, and it serves its purpose, it IS useful.
You forgot about one possibility: it may work but it's not the best
way to do it. I was trying to reason you to the better way but you got
defensive.
> Considering the patch is really tiny, I don't see the problem.
I am not deciding what goes in and what doesn't. However, I have
doubts in its usefulness.
> > Don't see how this can be useful...
>
> Well, what exactly you don't find useful?
This remark was about short_module_name that aliases all modules
that are named like this.
> > Let's try to stage a small project by the rules you gave above.
>
> No need to do that, the build system has been working for more than
> one year already, there's a whole project composed of lots of modules
> which uses it, you might look at it as reference (notice that the
> Makefile needs to be reworked and refactored, but the concept and the
> Makefile.tubs files are completely valid):
> http://cvs.sunsite.dk/viewcvs.cgi/aweb/
Do you think I have nothing else to do? You don't send patch and then
when asked where it is useful say "go study my build system". That's
bad manners.
> > foo/foo/DEPS := libfoo.so \ # short module name of type 2
> > bar/libbar.so # full module name
> >
> > $(distdir)/foo/foo: $(foo/foo/DEPS) # ???
> > g++ -o $@ $^
> >
> >
> > The last rules won't work because when we link we need real libraries,
> > their aliases are not good enough anymore.
>
> But the last rule is wrong anyway.
Well, I just followed your instructions. Here is the quote from your
previous email:
> Defining dependencies for a module is done this way:
>
> full_module_name/DEPS := module_name1 ... module_nameN
>
> where module_nameX can be either a full_module_name or a short_module_name
>
> The build system handles this by simply defining full_module_name and
> both variants of short_module_name as .ALIAS'es to
> $(distdir)/full_module_name, and then simply adds a rule like this:
>
> $(distdir)/full_module_name : $(full_module_name/DEPS)
don't bother to reply,
-boris
signature.asc
Description: Digital signature
- RFC: .ALIAS builtin pseudotarget, Fabio Alemagna, 2004/09/21
- Re: RFC: .ALIAS builtin pseudotarget, Noel Yap, 2004/09/21
- Re: RFC: .ALIAS builtin pseudotarget, Boris Kolpackov, 2004/09/21
- Message not available
- Re: RFC: .ALIAS builtin pseudotarget, Boris Kolpackov, 2004/09/22
- Re: RFC: .ALIAS builtin pseudotarget, Fabio Alemagna, 2004/09/23
- Re: RFC: .ALIAS builtin pseudotarget, Boris Kolpackov, 2004/09/23
- Re: RFC: .ALIAS builtin pseudotarget, Fabio Alemagna, 2004/09/23
- Re: RFC: .ALIAS builtin pseudotarget, Noel Yap, 2004/09/23
- Re: RFC: .ALIAS builtin pseudotarget,
Boris Kolpackov <=
- Re: RFC: .ALIAS builtin pseudotarget, Fabio Alemagna, 2004/09/23
- Re: RFC: .ALIAS builtin pseudotarget, Fabio Alemagna, 2004/09/23