On Mon, 2003-06-02 at 13:14, Sven Neumann wrote:
Although this works, it is a little hackish and it will link gimp-1.3
against the installed libraries which might differ from the versions
in your source tree. The correct way to do this is to use libtool:
libtool gdb app/gimp-1.3
Shouldn't
Hi,
Henrik Brix Andersen [EMAIL PROTECTED] writes:
On Mon, 2003-06-02 at 13:14, Sven Neumann wrote:
Although this works, it is a little hackish and it will link gimp-1.3
against the installed libraries which might differ from the versions
in your source tree. The correct way to do this is to
On Tue, 2003-06-03 at 18:07, Sven Neumann wrote:
Only if you don't have libtool installed. If you are developing from
CVS you need to have libtool in your path anyway. The copy that is
shipped with the tarball is just there to avoid a dependancy on
libtool for everyone who wants to compile the
Hi there,
I recently uploaded teh 1.3.14 source code, to start to look around the code.
Actually, I humbly intend to actvely join GIMP's development along the next
couple of months, if I can get enough of what is going on.
./configure, make make install went as smoothly as one could ever
On Sun, 1 Jun 2003, Joao S. O. Bueno wrote:
But what I do need now is a faster way to go from edit code to running gimp.
Make Install asctually eats out a lot of time on my system. Is it possible to
run the gimp-1.3 binary generated from make straight, without make-installing
it?
Of course
Hi,
Helvetix Victorinox [EMAIL PROTECTED] writes:
Once the linking part has been done by app/gimp-1.3, I just run
gdb app/.libs/gimp-1.3
Although this works, it is a little hackish and it will link gimp-1.3
against the installed libraries which might differ from the versions
in your source
Once the linking part has been done by app/gimp-1.3, I just run
gdb app/.libs/gimp-1.3
Helvetix
On Sun, Jun 01, 2003 at 04:35:02PM -0700, Nathan Carl Summers wrote:
On Sun, 1 Jun 2003, Joao S. O. Bueno wrote:
But what I do need now is a faster way to go from edit code to running gimp.
