On Wed, 20 Apr 2005 17:16:39 +0200 Tilman Sauerbeck [EMAIL PROTECTED] babbled:
(B
(B Carsten Haitzler [EMAIL PROTECTED] [2005-04-20 11:56]:
(B I suggest to handle this the same way we do it in Esmart:
(B "ecore-config --libs" only includes "-lecore", if you need the
(B subsystems,
On Wed, 20 Apr 2005 13:46:22 -0400 Michael Jennings [EMAIL PROTECTED] babbled:
(B
(B On Wednesday, 20 April 2005, at 17:16:39 (+0200),
(B Tilman Sauerbeck wrote:
(B
(B hmm - i see not big problem with this - as long as everything
(B updates to match... i guess we can just say "fuck it"
Carsten Haitzler [EMAIL PROTECTED] [2005-04-20 11:56]:
I suggest to handle this the same way we do it in Esmart:
ecore-config --libs only includes -lecore, if you need the
subsystems, you'll have to add the other linker switches yourself.
hmm - i see not big problem with this - as long as
Hi,
IMHO it sucks that if you want to link your application to Ecore, you
have to link in all of its subsystems. This isn't much of an issue for
the generic app that uses ecore_evas, but it sucks if all you need is
the E-ecore and the config subsystem e.g.
I suggest to handle this the same way we
On Tue, 2005-04-19 at 20:35 +0200, Tilman Sauerbeck wrote:
Hi,
IMHO it sucks that if you want to link your application to Ecore, you
have to link in all of its subsystems. This isn't much of an issue for
the generic app that uses ecore_evas, but it sucks if all you need is
the E-ecore and the
On 4/20/05, Tilman Sauerbeck [EMAIL PROTECTED] wrote:
Hi,
IMHO it sucks that if you want to link your application to Ecore, you
have to link in all of its subsystems. This isn't much of an issue for
the generic app that uses ecore_evas, but it sucks if all you need is
the E-ecore and the
On Tue, 19 Apr 2005 20:35:41 +0200 Tilman Sauerbeck [EMAIL PROTECTED] babbled:
(B
(B Hi,
(B IMHO it sucks that if you want to link your application to Ecore, you
(B have to link in all of its subsystems. This isn't much of an issue for
(B the generic app that uses ecore_evas, but it sucks if
