Can anybody point me to examples about how to use gimpwire lib?
Thanks and regards,Shrinivas Kulkarni.
On Sun, Dec 14, 2003 at 05:13:30PM +, Tor Lillqvist <[EMAIL PROTECTED]> wrote:
> I wonder, could the typical fork() immeditaly followed by exec() (in
> the child process) be somehow detected by Cygwin/MSYS, avoiding the
> need for emulating the full fork() semantics in this typical case?
No, b
On Sun, Dec 14, 2003 at 12:46:27PM +, Roger Leigh <[EMAIL PROTECTED]> wrote:
> MSYS does not depend on cygwin, BTW. It's entirely standalone.
Why do you claim this if a few simple checks could have convinced you
otherwise? At least the shell, which is just bash, is linked against
the cygwin
On Sun, Dec 14, 2003 at 09:29:07AM -0800, Manish Singh wrote:
> Yeah, gcc is quite slow at compile time, and I think in newer versions
> it's gotten slower, not faster.
>From the gcc3.4 changes.html:
* Precompiled headers are now supported. Precompiled headers can dramatically
speed up compilat
On Sunday 14 December 2003 21:29, Manish Singh wrote:
> On Sun, Dec 14, 2003 at 09:24:54PM -0200, Joao S. O. Bueno wrote:
> > On Sunday 14 December 2003 18:36, Manish Singh wrote:
> > > On Sun, Dec 14, 2003 at 05:41:59PM -0200, Joao S. O. Bueno
wrote:
> > > > Since it talks specifically about GIMP
On Sun, Dec 14, 2003 at 09:24:54PM -0200, Joao S. O. Bueno wrote:
> On Sunday 14 December 2003 18:36, Manish Singh wrote:
> > On Sun, Dec 14, 2003 at 05:41:59PM -0200, Joao S. O. Bueno wrote:
> > > Since it talks specifically about GIMP python,
> > > which me, by chance, was trying for the very fir
On Sunday 14 December 2003 18:36, Manish Singh wrote:
> On Sun, Dec 14, 2003 at 05:41:59PM -0200, Joao S. O. Bueno wrote:
> > Since it talks specifically about GIMP python,
> > which me, by chance, was trying for the very first time in gimp
> > 1.3 (no kidding --- I've been on gimp 1.2 with my pyth
On Sun, Dec 14, 2003 at 05:41:59PM -0200, Joao S. O. Bueno wrote:
>
> Since it talks specifically about GIMP python,
> which me, by chance, was trying for the very first time in gimp 1.3
> (no kidding --- I've been on gimp 1.2 with my python fu stuff so far),
> it is interesting to mention that
Since it talks specifically about GIMP python,
which me, by chance, was trying for the very first time in gimp 1.3
(no kidding --- I've been on gimp 1.2 with my python fu stuff so far),
it is interesting to mention that as of now gimpImage neither
gimp.pdb.gimp_image_new seens to be working. Th
Hi,
That reminds me of some mail I got from a guy who also proposed
prizes for GIMP functionality. I believe that he mailed to the
list, he also posted on Usenet a few times.
As a point of interest, what should we do when this kind of thing
happens? Debate the features, decide which we'd like to
Hi,
I'd like to draw your attention to this URL:
http://www.markshuttleworth.com/bounty.html
Sven
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
On Sun, Dec 14, 2003 at 02:26:03PM +0100, Jean-Luc Coulon (f5ibh) wrote:
> Hi,
>
> I cannot compile the cvs as libgimp/gimpmiscui.h has gone ..
>
> gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/local/include/glib-2.0
> -I/usr/local/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/
> gtk-2
On Sun, Dec 14, 2003 at 04:57:15PM +, Tor Lillqvist wrote:
> But I don't think the actual time it takes to run gcc is what annoys
> people most when building stuff that uses auto*/libtool on
> Windows. For me, the most annoying part is libtool. This shell-script
> is mind-bogglingly slow. Runni
On Sun, Dec 14, 2003 at 05:13:30PM +, Tor Lillqvist wrote:
> Roger Leigh writes:
> > They both have to implement fork() using Windows calls though,
> > which can never be efficient.
>
> (Just rambling here:)
>
> I wonder, could the typical fork() immeditaly followed by exec() (in
> the chil
Roger Leigh writes:
> MSYS does not depend on cygwin, BTW. It's entirely standalone.
MSYS is a *fork* (version) of Cygwin. As the mingw FAQ says, "The
POSIX layer used by MSYS is a fork of the 1.3.3 version of Cygwin".
(But maybe that was what you meant.)
> They both have to implement fork() u
Adam D. Moss writes:
> The only thing I can think of would be if the
> //etc headers that get pulled into just about
> every file on a win32 build expand into monsterous evil and add
> measurably to the unit compilation time.
Well, that probably is the reason. *is* quite large. But
none of t
Sven Neumann <[EMAIL PROTECTED]> writes:
> Hi,
>
> <[EMAIL PROTECTED] ( Marc) (A.) (Lehmann )> writes:
>
>> which is a severe shortcoming of the build environment (AFAIK, Msys
>> uses cygwin which is awfully slow due to a large number of
>> reasons).
MSYS does not depend on cygwin, BTW. It's ent
On Sun, Dec 14, 2003 at 01:08:20PM +, "Adam D. Moss" <[EMAIL PROTECTED]> wrote:
> As a data point, I use a (optimized build) mingw cross-compiler
> hosted on linux, and the raw compilation itself takes a lot longer
> (50% longer, or more) than the same compiler version built
That's interesting
On Sun, Dec 14, 2003 at 12:46:54PM +0100, Sven Neumann <[EMAIL PROTECTED]> wrote:
> This sounds like if you had a clue on what is causing the slowliness
> of running configure on Cygnus.
The biggest reason is very slow fork(), followed by extremely slow
select(), filehandle operations, pipes and m
Hi,
"Jean-Luc Coulon (f5ibh)" <[EMAIL PROTECTED]> writes:
> I cannot compile the cvs as libgimp/gimpmiscui.h has gone ..
This has been fixed in CVS already but probably the anoncvs server
hasn't caught up yet. Simply remove the inclusion of gimpmiscui.h
from libgimp/gimpui.h.
Sven
Hi,
I cannot compile the cvs as libgimp/gimpmiscui.h has gone ..
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I.. -I/usr/local/include/glib-2.0
-I/usr/local/lib/glib-2.0/include -I/usr/include/gtk-2.0 -I/usr/lib/
gtk-2.0/include -I/usr/include/atk-1.0 -I/usr/include/pango-1.0 -I/
usr/include/freetype2 -
Sven Neumann wrote:
which is a severe shortcoming of the build environment (AFAIK, Msys
uses cygwin which is awfully slow due to a large number of
reasons).
This sounds like if you had a clue on what is causing the slowliness
of running configure on Cygnus. I recently compiled the Blinkenlights
so
Hi,
<[EMAIL PROTECTED] ( Marc) (A.) (Lehmann )> writes:
> which is a severe shortcoming of the build environment (AFAIK, Msys
> uses cygwin which is awfully slow due to a large number of
> reasons).
This sounds like if you had a clue on what is causing the slowliness
of running configure on Cygn
23 matches
Mail list logo
