David Neary wrote:
> It seems that the thing which is annoying my compiler
> is teh doubling of the % signs - with one % all passes well, with
> two, not so well. A sligntly modified configure confirms this.
>
> Are the two %s necessary to prefix the mm registers?
This is, of course, nonesense.
Sven Neumann wrote:
> Hi David,
>
> could you please test the attached diff to configure.in. It should
> find the problem with your compiler and it even simplifies things a
> bit.
I have stried, and my computer passes the mmx test with flying
colours :) It seems that the thing which is annoying
On Thu, 10 Jul 2003 19:25:22 +0200
Sven Neumann <[EMAIL PROTECTED]> wrote:
>
> > The attitude I keep encountering is a strong resistance to progress.
>
> Sorry, but removing features looks more like a regression to me.
>
I agree, but if on the second window there is 2 buttons, one to skip the
Hi,
Alan Horkan <[EMAIL PROTECTED]> writes:
> You are telling me that most of the programs in Gnome and KDE are
> wrong and the GIMP is right. I will go and read the GPL again and I
> will read the GPL FAQ and see if I can figure out where is this
> explicit requirement to display the license.
On Thu, 10 Jul 2003, Sven Neumann wrote:
> The point is that the GPL explicitely asks to present the user with
You are telling me that most of the programs in Gnome and KDE are wrong
and the GIMP is right.
I will go and read the GPL again and I will read the GPL FAQ and see if I
can figure out w
[EMAIL PROTECTED] (2003-07-10 at 1140.21 -0400):
> It is very sad to see that Sven thinks that Robin Rowe is the only
> person to whom his ideas should be told. Pity the rest of the GIMP
> developers (current and future) who might like to comment on it.
Use the list archives. Search engines let
Hi,
Helvetix Victorinox <[EMAIL PROTECTED]> writes:
> This isn't quite ready to go yet. But thanks for the note. The
> default build behaviour right now is to not build the new code.
Please, if possible, let the code be build. We need as much testing as
possible and we lack experience with bui
Hi,
Christopher Curtis <[EMAIL PROTECTED]> writes:
>> We actually had something else in mind but since you don't seem to be
>> interested I won't waste my time explaining our ideas.
>
> It is very sad to see that Sven thinks that Robin Rowe is the only
> person to whom his ideas should be told.
This isn't quite ready to go yet. But thanks for the note. The default
build behaviour right now is to not build the new code.
Helvetix
On Thu, Jul 10, 2003 at 08:36:44AM +0200, David Neary wrote:
>
> Hi,
>
> The new MMX composite code in the 1.3 tree doesn't build for me -
> am I the only o
Sven Neumann wrote:
We actually had something else in mind but since you don't seem to be
interested I won't waste my time explaining our ideas.
It is very sad to see that Sven thinks that Robin Rowe is the only
person to whom his ideas should be told. Pity the rest of the GIMP
developers (curr
Hi,
"Robin Rowe" <[EMAIL PROTECTED]> writes:
>> A 640x480 8-bit image file example.cpx would be laid out something like
>> this:
>>
>>
>> > data=...[921,600 raw bytes]...>
I am sorry but this format may look like XML but it doesn't follow the
XML specification. You cannot include binary data as
Hi David,
could you please test the attached diff to configure.in. It should
find the problem with your compiler and it even simplifies things a
bit.
Sven
Index: configure.in
===
RCS file: /cvs/gnome/gimp/configure.in,v
retrieving
Hi,
David Neary <[EMAIL PROTECTED]> writes:
> The new code is missing a #ifdef somewhere, I think - perhaps
> composite-mmx.c shouldn't be build at all if USE_MMX isn't
> defined... but that's another issue.
I've added an #ifdef that causes the file content to be skipped. I
prefer #ifdefs over a
Hi,
David Neary <[EMAIL PROTECTED]> writes:
> That said, some day soon, the GIMP developers are going to have
> to get together for a brainstorning session about how we can
> communicate better with the user base, and vice versa. With IRC,
> Bugzilla, 2 mailing lists, usenet, the [EMAIL PROTECTED
Hi,
indeed there was an #ifdef missing. My latest commit should fix the
build for you. Can you please check config.log nevertheless since I'd
like to make sure that the configure check did it's job correctly.
These new checks could need some more testing. So if you are on an
obscure hardware-plat
Sven Neumann wrote:
> Hi,
>
> David Neary <[EMAIL PROTECTED]> writes:
>
> > The new MMX composite code in the 1.3 tree doesn't build for me -
> > am I the only one? My processor is a 350MHz K6-2 with mmx
> > support, and the error says that there are a bunch (6, I think)
> > of unknown registers
Hi,
David Neary <[EMAIL PROTECTED]> writes:
> The new MMX composite code in the 1.3 tree doesn't build for me -
> am I the only one? My processor is a 350MHz K6-2 with mmx
> support, and the error says that there are a bunch (6, I think)
> of unknown registers in the asm (%mm0, %mm1, ...).
The c
Ernst,
> Couldn't both teams try to find a common format?
In theory yes, but it seems unlikely.
Sven said today that GIMP has been (privately) discussing a new XML-based
file format for GIMP for more than three years -- which is the first I've
heard of it. However, no spec has been made availabl
Hi,
"Joao S. O. Bueno" <[EMAIL PROTECTED]> writes:
> the cross posting with the Cinepaint guys brougth this to light.
> So there is something being done about a XML file format
> to the GIMP.
>
> How is it's development going on?
Some developers brainstorm about it from time to time. That's abou
Hi,
Alan Horkan <[EMAIL PROTECTED]> writes:
>> The information about the files that are installed in the user
>
> The dialog tells you what the names of the files that are going to be
> installed but not their purpose or roughly how much space they will take.
You need to play with the dialog a l
David,
> As a proposal for a modification which would bring back
> compatibility, we could expand the header by 4 bytes to include
> bit depth (8 or 16), which could then be factored into the load
> routines of both our apps (we would crush 16 bit nbrushes down to
> 8 bits, and you would expand 8
Hi,
The new MMX composite code in the 1.3 tree doesn't build for me -
am I the only one? My processor is a 350MHz K6-2 with mmx
support, and the error says that there are a bunch (6, I think)
of unknown registers in the asm (%mm0, %mm1, ...).
I'm mailing this to the list because, to be quite hon
22 matches
Mail list logo
