On Thu, 3 Sep 2009, Albin Tonnerre wrote:

> On Thu, Sep 03, 2009 at 11:02:34PM +0200, Vincent Torri wrote :
>>
>>
>> On Thu, 3 Sep 2009, Albin Tonnerre wrote:
>>
>>> On Fri, Sep 04, 2009 at 03:36:28AM +0700, Mikhail Gusarov wrote :
>>>>
>>>> Twas brillig at 22:30:44 03.09.2009 UTC+02 when vto...@univ-evry.fr did 
>>>> gyre and gimble:
>>>>
>>>> VT> Looks good to me. I've looked at others .og files (in fontconfig
>>>> VT> for example), and I have seen a Libs.private. SHould it be used ?
>>>>
>>>> Yes, of course!
>>>>
>>>> The rule of thumb is "when something is not needed to link with a shared
>>>> library, it goes to {Requires,Libs}.private"
>>>
>>> As far as the EFL are concerned Requires.private can replace Requires 
>>> virtually
>>> everywhere, however this is not true /at all/ for Libs.
>>>
>>> In fact, most of what's in Libs currently shouldn't move to Libs.private,
>>> because they actually are justified.
>>
>> are you sure ?
>>
>> http://people.freedesktop.org/~dbn/pkg-config-guide.html
>>
>> shouln't -liconv be in Libs.private ?
>
> [23:35 ~/e17/svn/trunk:svn|r42212]% find -name \*.pc.in  | xargs grep iconv
> zsh: done       find -name \*.pc.in |
> zsh: exit 123   xargs grep iconv

replace .pc.in by .pc ;)
or faster, look in ecore-txt.pc

Vincent

>
> I've never stated that Libs and Libs.private were all correctly set. I said 
> that
> *most* of what is currently in Libs shouldn't move to Libs.private, and that's
> correct.
>
> Regards,
> -- 
> Albin Tonnerre
>

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel

Reply via email to