Re: [Gimp-developer] opencl error - gegl won't build without hard-resetting to an earlier version
It looks like the problem is that this script depends of Python 2.x and you're using Python 3.x. The script should be updated.. ? On Mon, Oct 28, 2013 at 12:51 PM, Elle Stone ellest...@ninedegreesbelow.com wrote: I did git pull for gegl, tried to build, and got this error: Making all in opencl make[2]: Entering directory `/home/elle/code/gimp291/**build/gegl/opencl' /usr/bin/python ./cltostring.py bilateral-filter-fast.cl Traceback (most recent call last): File ./cltostring.py, line 56, in module line = escape_string(line) File ./cltostring.py, line 31, in escape_string if isinstance(s, unicode): NameError: global name 'unicode' is not defined make[2]: *** [bilateral-filter-fast.cl.h] Error 1 make[2]: Leaving directory `/home/elle/code/gimp291/**build/gegl/opencl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/elle/code/gimp291/**build/gegl' make: *** [all] Error 2 So I hard-reset Gegl to October 24th, commit 24580c4f4395be162a5e19b51681dd**90d8639b59 and got the same error. So I hard-reset Gegl all the way back to September 1, and Gegl built without any problem. My computer doesn't play nice with opencl, if that is relevant. Is there a way to disable opencl before building? -- Elle Stone http://ninedegreesbelow.com Articles on color management and open source photography __**_ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/**mailman/listinfo/gimp-** developer-listhttps://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GEGL Gaussian Blur (Gimp/gegl git)
I actually was looking at it when I realized Daniel solved the problem :) On Sun, Oct 27, 2013 at 2:44 PM, Partha Bagchi parth...@gmail.com wrote: Victor must have done some magic since he sent me an email saying that he was looking into the OpenCL bug. I can now say that this is gone and in fact GEGL is considerably more stable. I can actually work on 16-bit tiffs without crashing! :) I was so excited about this that I rebuilt both Windows and Mac and posted on my website. Thanks devs! Partha On Sat, Oct 12, 2013 at 7:47 AM, Partha Bagchi parth...@gmail.com wrote: Further information to my post. I built on Windows 7 64-bit and here I have 16G of RAM with dedicated Nvidia graphics. It crashes my video driver (which is able to recover) and then Gimp dies with this following. This is after graphics card recovery and then opening c2g. Here is the error message: bps: 16 load_contiguous bytes_per_pixel: 6, format: 6 file-tiff-load.exe is updating the progress too often Parsing 'C:\Users\partha\AppData\Roaming\GIMP\2.9\filters\GimpGegl-gegl-gaussian-blur-config.settings' (gimp-2.9.exe:9400): GEGL-gaussian-blur.c-WARNING **: Error in gaussian-blur.c:519@cl_gaussian_blur - mem object allocation failure Writing 'C:\Users\partha\AppData\Roaming\GIMP\2.9\filters\GimpGegl-gegl-gaussian-blur-config.settings' Parsing 'C:\Users\partha\AppData\Roaming\GIMP\2.9\filters\GimpGegl-gegl-c2g-config.settings' (script-fu.exe:6928): LibGimpBase-WARNING **: script-fu.exe: gimp_wire_read(): error On Sat, Oct 12, 2013 at 12:21 AM, Partha Bagchi parth...@gmail.comwrote: I am finding that one possible show stopper is the gegl gaussian blur. Here is a simple example. Open a 16bit, say 12 MP tiff image. Duplicate Layer, and run gegl gaussian blur with x=y=100. On my Macbook Pro with 8G RAM, either I will get vertical lines on the layer (at best) or crash my Mac. Is there a way to speed up gaussian blur or is this a Mac issue and never happens on Linux? Thanks, Partha ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Parallelization project (for students)
Ooops, sorry. I think I haven't sent the e-mail to the list. Here it is: Hi Thomas, I've been working with OpenCL in GEGL. I think there is a need in GEGL for a multi-threading code-path. But the work necessary for it is far from trivial, I know Daniel has been working on this so I'm copying him. On Sat, Jul 13, 2013 at 4:52 AM, scl scl.gp...@gmail.com wrote: On 13.07.13 at 01:22 AM Jon Nordby wrote: A Google Summer of Code project is also taking place for porting filters from GIMP to GEGL. This work is mentored by Victor Oliviera (victorm) and done by Carlos Zubieta (zurwolf) , so you should probably check in with them. http://wiki.gimp.org/index.**php/Hacking:GSoC/2013/Ideashttp://wiki.gimp.org/index.php/Hacking:GSoC/2013/Ideas So if working with OpenCL is not a problem, there is plenty of suitable work. The nice thing about operations for student work is that they are self-contained and can be understood quite easily in isolation. I fully agree with you in these two points. Yet I haven't seen much traffic in this GSoC item this year (sorry, if I'm seeing it wrong), so help might be welcome. 1) wiki pages may be out of date Basically you're right. They are not updated immediately. Lately I've updated the GSoC page to insert more helpful references. The GEGL porting matrix is updated regularly, the last time on 07.07.2013. Updating it on every end of month and inserting the missing changes is on my list of periodic tasks. If something important is missing, I'd be grateful for suggestions. Kind regards, Sven __**_ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/**mailman/listinfo/gimp-** developer-listhttps://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list List address:gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Selective gaussian blur port to gegl
Just a comment, I implemented recently a much faster version of the
bilateral-filter. Though I think there is still some polishing to do,
it is basically working in the CPU and the GPU.
On Sat, Apr 6, 2013 at 4:39 PM, Øyvind Kolås pip...@gimp.org wrote:
Thank you for poking around looking for more things to bring over to GEGL. I
do not know much about the GIMP plug-in, but can tell you some other bits of
information that could be relevant ;)
The core part of selective gaussian blur is what is normally called
bilateral filtering in academic image processing circles. GEGL already has
a (rather slow) bilateral filter implemented contained in
operations/common/bilateral-filter.c
The specifics of the behavior of GIMPs selective-gaussian blur is something
I'd consider a historic artifact - that we might not want to preserve in
future versions.
(As to the lines you've pointed out, looking at them in isolation.. this
seems to be code that deals with correctly handling alpha; GEGL does this
normally by processing buffers with premultiplied alpha, this seems to be
manual hacks that scales the contribution of pixels to the sum by the
alpha.. and since legacy GIMP is 8bpc, = 8, is the same as /256 and 256
is 1.0, which normalizes the effect of multiplying by the alpha values
between 0 and 255.)
/Ø
On Sat, Apr 6, 2013 at 12:14 PM, Karthikeyan S karthikde...@gmail.com
wrote:
Hi all,
I am trying to port the selective gaussian blur filter to gegl. I do not
understand the following lines in the original gimp code and what purpose
they serve.
---
Line 668
if (has_alpha)
d *= src_b[nb - b]; // ?
---
Line 676
if (has_alpha)
{
rowsum = 8; // why?
rowfact = 8;
}
---
Also, as of now, my implementation correctly maintains edges in checker
board images while blurring other areas. I am trying to debug another issue
wherein I see that the noise pixels (in complete dark background in the
checkerboard image) seem to get smeared out to neighbourhood areas and we
get large patches of white arround the blurred pixel (This does not happen
in gimp implementation). I am trying to see if the above lines have some
clue to that.
Thanks,
Karthik
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
--
«The future is already here. It's just not very evenly distributed»
-- William Gibson
http://pippin.gimp.org/http://ffii.org/
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
___
gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Our application for GSoC
Sorry guys, I just realized it has been already done :) On Sun, Mar 24, 2013 at 10:35 PM, Victor Oliveira victormath...@gmail.comwrote: Hello everyone, The application for mentoring orgs this year close on March 29, next week. I'm not sure if someone has already applied, but let's do it? Victor ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GEGL Crashes GPU
Hi Partha, I couldn't really reproduce your error, so I assume it is because you're trying to use the display GPU for processing and to avoid blocking the screen, the nvidia driver just kills whatever is running in the GPU. Also, I'm not sure if you're already using the GEGL_SWAP=RAM option to run GIMP, it should improve performance and maybe you don't get this error. On Sat, Feb 16, 2013 at 12:29 AM, Partha Bagchi parth...@gmail.com wrote: Hi Victor, I have an NVIDIA GPU with 1G dedicated VRAM, i7 Core CPU, and 16G of RAM. In any case, 150x150 radius should be doable. In any case, I am sure that when Gimp goes production, it's bound to come up. Any further report on Mac? While I am finding that it's quite fast on an Mac with 8G RAM, I am not sure if the GPU is being used. Note that everything I have seen/ read about OpenCL says that you don't need to load the library at least on a Mac. Thanks, Partha On Fri, Feb 15, 2013 at 7:22 PM, Victor Oliveira victormath...@gmail.comwrote: Hi Partha, Thanks for the bug report, I'll give a look when I can. Notice that a 150x150 radius is very big and maybe yout GPU doesn't have enough memory for that, but it was supposed to fallback to the CPU in this case. Thanks Victor On Fri, Feb 15, 2013 at 8:47 AM, Tobias Ellinghaus h...@gmx.de wrote: Am Freitag, 15. Februar 2013, 04:52:49 schrub Partha Bagchi: Hi Victor, Latest git. I have an NVIDIA GeForce GT 230M card with 1G VRAM. The opengl version is 1.1 CUDA 4.2.1 etc. Windows 7 64bit I think OpenCL is taking down my video every time. Here is a simple repeatable test for me. 1. Open 16 bit tiff. 2. Duplicate layer. 3. Layer - desaturate - invert 4. GEGL gaussian blur x = y = 150. Takes the screen down (goes black and recovers) and leaves a dark tile on the layer. Any ideas? That is normal when running OpenCL (or CUDA) kernels on a GPU that has a monitor connected. On Windows it will time out quite quickly, on Linux AFAIK not. However, that can be configured. Google is your friend, just search for nvidia watchdog. [...] Thanks, Partha Tobias ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] GEGL Crashes GPU
Hi Partha, Thanks for the bug report, I'll give a look when I can. Notice that a 150x150 radius is very big and maybe yout GPU doesn't have enough memory for that, but it was supposed to fallback to the CPU in this case. Thanks Victor On Fri, Feb 15, 2013 at 8:47 AM, Tobias Ellinghaus h...@gmx.de wrote: Am Freitag, 15. Februar 2013, 04:52:49 schrub Partha Bagchi: Hi Victor, Latest git. I have an NVIDIA GeForce GT 230M card with 1G VRAM. The opengl version is 1.1 CUDA 4.2.1 etc. Windows 7 64bit I think OpenCL is taking down my video every time. Here is a simple repeatable test for me. 1. Open 16 bit tiff. 2. Duplicate layer. 3. Layer - desaturate - invert 4. GEGL gaussian blur x = y = 150. Takes the screen down (goes black and recovers) and leaves a dark tile on the layer. Any ideas? That is normal when running OpenCL (or CUDA) kernels on a GPU that has a monitor connected. On Windows it will time out quite quickly, on Linux AFAIK not. However, that can be configured. Google is your friend, just search for nvidia watchdog. [...] Thanks, Partha Tobias ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] multithreading and GEGL
Hello Partha. I'm sorry, I mean --enable-debug instead of --enable-config. That's a good observation. In Windows I look for OpenCL.dll and in Linux I look for libOpenCL.so, but I'm not sure how I should handle it in MacOS. I was assuming it was the same as the Linux way. Do you know how I should do this? Victor On Fri, Feb 1, 2013 at 8:10 PM, Partha Bagchi parth...@gmail.com wrote: Victor, When I look at the code, I don't understand how you are handling the Mac OS, when you don't typically see so libraries, by dylibs. Can you elaborate? Also, when I try to add --enable-config to configure, I get configure: WARNING: unrecognized options: --enable-config Thanks, Partha On Tue, Jan 29, 2013 at 12:32 PM, Victor Oliveira victormath...@gmail.com wrote: yes, export GEGL_ENABLE_OPENCL=yes also, when you build GEGL, put the option --enable-config. with that you can set: export GEGL_DEBUG=opencl so you can see if OpenCL is really being used or if there is some bug. Victor On Tue, Jan 29, 2013 at 11:31 AM, Paka ptilopt...@gmail.com wrote: * Victor Oliveira victormath...@gmail.com [01-29-13 07:39]: You can use OpenCL in the CPU, just install the AMD OpenCL SDK. GEGL looks for libOpenCL.so in /usr/lib. You should use GEGL_ENABLE_OPENCL=yes export as environment varible or ?? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] multithreading and GEGL
On Fri, Feb 1, 2013 at 11:10 PM, Partha Bagchi parth...@gmail.com wrote: Hi Victor, I think on Windows for 32-bit you are OK with call OpenCL.dll, but I think you need to call OpenCL64.dll for 64-bit? I have a 64-bit Windows system and it comes with OpenCL.dll. For Mac, according to http://developer.apple.com/library/mac/documentation/Performance/Conceptual/OpenCL_MacProgGuide/OpenCL_MacProgGuide.pdf the sample code on page 17, says: // This include pulls in everything you need to develop with OpenCL on OS X v10.7. #include OpenCL/opencl.h To compile from the command line, I think you need to do have -framework OpenCL during compilation. For instance, gcc -framework OpenCL filein.c -o filein Can we test this out? The problem is, I don't have a machine with MacOS :/ Thanks, Partha On Fri, Feb 1, 2013 at 7:30 PM, Victor Oliveira victormath...@gmail.com wrote: Hello Partha. I'm sorry, I mean --enable-debug instead of --enable-config. That's a good observation. In Windows I look for OpenCL.dll and in Linux I look for libOpenCL.so, but I'm not sure how I should handle it in MacOS. I was assuming it was the same as the Linux way. Do you know how I should do this? Victor On Fri, Feb 1, 2013 at 8:10 PM, Partha Bagchi parth...@gmail.com wrote: Victor, When I look at the code, I don't understand how you are handling the Mac OS, when you don't typically see so libraries, by dylibs. Can you elaborate? Also, when I try to add --enable-config to configure, I get configure: WARNING: unrecognized options: --enable-config Thanks, Partha On Tue, Jan 29, 2013 at 12:32 PM, Victor Oliveira victormath...@gmail.com wrote: yes, export GEGL_ENABLE_OPENCL=yes also, when you build GEGL, put the option --enable-config. with that you can set: export GEGL_DEBUG=opencl so you can see if OpenCL is really being used or if there is some bug. Victor On Tue, Jan 29, 2013 at 11:31 AM, Paka ptilopt...@gmail.com wrote: * Victor Oliveira victormath...@gmail.com [01-29-13 07:39]: You can use OpenCL in the CPU, just install the AMD OpenCL SDK. GEGL looks for libOpenCL.so in /usr/lib. You should use GEGL_ENABLE_OPENCL=yes export as environment varible or ?? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] multithreading and GEGL
You can use OpenCL in the CPU, just install the AMD OpenCL SDK. GEGL looks for libOpenCL.so in /usr/lib. You should use GEGL_ENABLE_OPENCL=yes On Tue, Jan 29, 2013 at 1:24 AM, Alexander Rabtchevich alexander.v.rabtchev...@gmx.net wrote: I have embedded AMD 4290 graphics, which does not support OpenCL. So trying ENABLE_OPENCL=yes doesn't make any difference. And the processor is 6-cores Phenom II 1075T. With respect, Alexander Rabtchevich Victor Oliveira wrote: You could try the OpenCL support in GEGL, it should use all of your cores. ps: there are bugs still, but I'm solving them. Victor On Mon, Jan 28, 2013 at 4:27 PM, Alexander Rabtchevich alexander.v.rabtchev...@gmx.net wrote: Hello Is there a way to make 2.9 git master to use more than one core? Changing in GIMP settings doesn't make effect. With respect, Alexander Rabtchevich ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] multithreading and GEGL
yes, export GEGL_ENABLE_OPENCL=yes also, when you build GEGL, put the option --enable-config. with that you can set: export GEGL_DEBUG=opencl so you can see if OpenCL is really being used or if there is some bug. Victor On Tue, Jan 29, 2013 at 11:31 AM, Paka ptilopt...@gmail.com wrote: * Victor Oliveira victormath...@gmail.com [01-29-13 07:39]: You can use OpenCL in the CPU, just install the AMD OpenCL SDK. GEGL looks for libOpenCL.so in /usr/lib. You should use GEGL_ENABLE_OPENCL=yes export as environment varible or ?? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] multithreading and GEGL
no, besides building gegl by yourself, no. GIMP doesn't require OpenCL because the libOpenCL.so is loaded at runtime (like, dlopen) in the case it is present at the machine. Victor On Tue, Jan 29, 2013 at 3:57 PM, Paka ptilopt...@gmail.com wrote: * Victor Oliveira victormath...@gmail.com [01-29-13 12:34]: yes, export GEGL_ENABLE_OPENCL=yes also, when you build GEGL, put the option --enable-config. with that you can set: export GEGL_DEBUG=opencl so you can see if OpenCL is really being used or if there is some bug. tks, I added to ~/.bashrc as I use pre-packaged rpm. I cannot see that opencl is required or used by gimp, as rpm -q gimp --requires does not show opencl is there a test to show usage other than dis-abling, timing an action, and enabling and timing same action? tks, -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.orgPhoto Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535@ http://linuxcounter.net ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] multithreading and GEGL
You could try the OpenCL support in GEGL, it should use all of your cores. ps: there are bugs still, but I'm solving them. Victor On Mon, Jan 28, 2013 at 4:27 PM, Alexander Rabtchevich alexander.v.rabtchev...@gmx.net wrote: Hello Is there a way to make 2.9 git master to use more than one core? Changing in GIMP settings doesn't make effect. With respect, Alexander Rabtchevich ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Nightly Builds
This is awesome work :) On Fri, Aug 10, 2012 at 5:25 PM, drawoc dra...@darkrefraction.com wrote: I just added a README to the github repository in my first email. Let me know if the scripts give you any trouble. -- drawoc On Thu, Aug 9, 2012 at 5:13 PM, Jari Niskala jarinisk...@gmail.com wrote: That's great drawoc! Any chance you have any writeup/info on how to setup to run this locally? Any info, no matter how small greatly appreciated. Thanks! -Jari -Original Message- From: gimp-developer-list-boun...@gnome.org [mailto:gimp-developer-list-boun...@gnome.org] On Behalf Of drawoc Sent: Thursday, August 09, 2012 1:10 PM To: gimp-developer-list@gnome.org Subject: [Gimp-developer] Nightly Builds I've set up a machine to do start doing nightly builds of the GIMP for Windows. Anyone who's interested can find them here: http://nightly.darkrefraction.com/gimp/ I've also uploaded my jhbuild scripts to github: https://github.com/drawoc/windows-gimp-jhbuild -- drawoc ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] [Gegl-developer] Windows development
On Tue, May 8, 2012 at 7:32 PM, Jasper van de Gronde th.v.d.gro...@hccnet.nl wrote: Thanks for the info. This should get me at least a bit further. I might try using a LiveCD or something to cross-compile. Again thanks for the information. BTW, did you do your Windows experiment using the normal mingw, or using TDM's GCC? The normal one :p On 2012-05-07 00:37, Victor Oliveira wrote: As far as I know, there are really few Windows developers for GIMP (one or two?), basically, all development is done on Linux and because of that, Windows-only problems are discovered just at the end of the release cycle. I spent a long time trying to discover how to compile GIMP in Windows, even though I'm a Linux developer, I needed to run it in Windows for my OpenCL work because my GPU doesn't have a Linux driver. At first, I tried to use MinGW+MSYS in Windows, it worked, but it is _extremely_ slow... like 3~4 hours to build GIMP and dependencies. Also, it had some random bugs. Much better is to use mingw-w64 in Linux to build Windows binaries. Anyway, here is what I've been doing. System: Ubuntu 12.04LST 1. Install mingw-w64 2. use the grab-stuff.sh script (from Ender) to download precompiled packages from OpenSUSE repositories, change your prefix in the script 3. What we need will be extracted to ./usr/x86_64-w64-mingw32/sys-root/mingw 4. set your environment vars like the env.sh file (change to your directories) 5. get babl, gegl and gimp from git and build it: $ cd babl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no ; make ; make install $ cd gegl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no --disable-docs; make ; make install $ cd gimp $ ./configure --prefix=$PREFIX --without-dbus --without-gudev --without-linux-input --without-xmc --disable-python --host=x86_64-w64-mingw32 --without-libjpeg; make ; make install I had problems with a -pthreads flag (which breaks mingw), it seems my system was polluted and I had a autotools file somewhere including it, I couldn't find the file. so my brute force solution was to have an Ubuntu VM with a clean system :/ and that's it... bye! Victor On Sat, May 5, 2012 at 10:32 AM, gfxuser gfx.u...@online.de wrote: On 05/05/2012 at 09:52 Victor Oliveira wrote: I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux. Hi Victor, could you please put a finer point on this? Is this for GEGL only or for GIMP, too? Which tools do you use in Windows? Mitch regretfully noticed in a bug report lately that there are no Windows developers for GIMP. Maybe your informations could help to bring more Windows developers into the project. Best regards, grafxuser ___ gegl-developer-list mailing list gegl-developer-l...@gnome.org http://mail.gnome.org/mailman/listinfo/gegl-developer-list ___ gegl-developer-list mailing listgegl-developer-list@gnome.orghttp://mail.gnome.org/mailman/listinfo/gegl-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] [Gegl-developer] Windows development
As far as I know, there are really few Windows developers for GIMP (one or two?), basically, all development is done on Linux and because of that, Windows-only problems are discovered just at the end of the release cycle. I spent a long time trying to discover how to compile GIMP in Windows, even though I'm a Linux developer, I needed to run it in Windows for my OpenCL work because my GPU doesn't have a Linux driver. At first, I tried to use MinGW+MSYS in Windows, it worked, but it is _extremely_ slow... like 3~4 hours to build GIMP and dependencies. Also, it had some random bugs. Much better is to use mingw-w64 in Linux to build Windows binaries. Anyway, here is what I've been doing. System: Ubuntu 12.04LST 1. Install mingw-w64 2. use the grab-stuff.sh script (from Ender) to download precompiled packages from OpenSUSE repositories, change your prefix in the script 3. What we need will be extracted to ./usr/x86_64-w64-mingw32/sys-root/mingw 4. set your environment vars like the env.sh file (change to your directories) 5. get babl, gegl and gimp from git and build it: $ cd babl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no ; make ; make install $ cd gegl $ ./configure --prefix=$PREFIX --host=x86_64-w64-mingw32 --enable-introspection=no --disable-docs; make ; make install $ cd gimp $ ./configure --prefix=$PREFIX --without-dbus --without-gudev --without-linux-input --without-xmc --disable-python --host=x86_64-w64-mingw32 --without-libjpeg; make ; make install I had problems with a -pthreads flag (which breaks mingw), it seems my system was polluted and I had a autotools file somewhere including it, I couldn't find the file. so my brute force solution was to have an Ubuntu VM with a clean system :/ and that's it... bye! Victor On Sat, May 5, 2012 at 10:32 AM, gfxuser gfx.u...@online.de wrote: On 05/05/2012 at 09:52 Victor Oliveira wrote: I really don't recommend you compiling it in Windows (it's slow and full of bugs). You should do cross-compiling in Linux. Hi Victor, could you please put a finer point on this? Is this for GEGL only or for GIMP, too? Which tools do you use in Windows? Mitch regretfully noticed in a bug report lately that there are no Windows developers for GIMP. Maybe your informations could help to bring more Windows developers into the project. Best regards, grafxuser __**_ gegl-developer-list mailing list gegl-developer-l...@gnome.org http://mail.gnome.org/mailman/**listinfo/gegl-developer-listhttp://mail.gnome.org/mailman/listinfo/gegl-developer-list env.sh Description: Bourne shell script download-mingw-rpm.py Description: Binary data grab-stuff.sh Description: Bourne shell script ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] trying to cross-compile GIMP - problem with pthreads
Hello everyone, I've been trying to cross-compile GIMP and I think I'm close, but there is an error that I couldn't find a way through. After building BABL and GEGL with success, I have the following error: CCLD gimp-console-2.8.exe x86_64-w64-mingw32-gcc: error: unrecognized option '-pthread' config.log: http://pastebin.com/R4LnZ0U0 make log: http://pastebin.com/HxJLmnUB I'm using MinGW-w64: victorm@trinity-laptop ~/gimp_windows/gimp $ x86_64-w64-mingw32-gcc -v Using built-in specs. COLLECT_GCC=x86_64-w64-mingw32-gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-w64-mingw32/4.6.1/lto-wrapper Target: x86_64-w64-mingw32 ... Thread model: win32 gcc version 4.6.1 (GCC) I feel I'm getting closer to finally cross-build GIMP, but please help :) ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] OpenCL support in GEGL is almost there
Hello everyone, I'm a GEGL developer and I've been working since last year implementing OpenCL support in GEGL. We have for now: - An API to write OpenCL point and area operations - A way to share image data between operations in the GPU (so we don't have to bring the image back and forth the CPU for each operator) - +20 GEGL operations have OpenCL support already - It's fast - It's been included in GIMP 2.8RC1 Darktable has its own OpenCL support code (which is pretty good, by the way). I'd like to start talks to avoid work repetition in both programs and to make an argument pro-GEGL use in Darktable :) bye! Victor Oliveira ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] academic references for GIMP
Hello people, Does anyone know about academic references for GIMP? Like papers I can cite? I'm doing a paper about my work with OpenCL and I need some bibliography :) Thanks! Victor Oliveira ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] lgm 2012
I wanna go :) On Thu, Feb 9, 2012 at 6:29 PM, Nicolas Robidoux nicolas.robid...@gmail.com wrote: I may go. (Not sure yet.) -- Nicolas Robidoux Image processing and applied mathematics consultant https://www.ohloh.net/accounts/NicolasRobidoux nicolas.robid...@gmail.com ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Undefined reference to __sync_fetch_and_sub_4
Hi, I'm running on the same problem today. I think it's a problem with glib atomic operations and mingw, because __sync_fetch_and_sub_4 is used in g_atomic_int_dec_and_test I suppose. But I'm stuck on that. I'm using the glib 2.30.2 build from OpenSUSE, so maybe the problem is there. Victor Oliveira On Fri, Nov 25, 2011 at 10:15 PM, Partha Bagchi parth...@gmail.com wrote: Hi All, Updated glib to 2.30.2 and gtk+-2.0 to 2.24.8. Using gcc 4.6.1. The latest geg download from ftp://gimptest.flamingtext.com/pub/nightly-tarballs/ is giving me the following error when building for win32 on Windows 7: Creating library file: .libs/libgegl-0.1.dll.a ../gegl/buffer/.libs/libbuffer.a(gegl-tile.o):gegl-tile.c:(.text+0x36): undefined reference to `__sync_fetch_and_sub_4' collect2: ld returned 1 exit status make[3]: *** [libgegl-0.1.la] Error 1 make[3]: Leaving directory `/usr/src/gimp/gimp-2.7.4/gegl-0.1.7/gegl' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/gimp/gimp-2.7.4/gegl-0.1.7/gegl' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/gimp/gimp-2.7.4/gegl-0.1.7' make: *** [all] Error 2 Any suggestions welcome. Thanks, Partha ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
Re: [Gimp-developer] Werror=missing-prototypes
Hi guys, I had to make these prototypes in order to build GIMP today, so I've just commited them. On Sun, Dec 18, 2011 at 5:13 PM, Partha Bagchi parth...@gmail.com wrote: 2011/12/18 Jernej Simončič jer...@ena.si: On Sunday, December 18, 2011, 18:43:07, Mukund Sivaraman wrote: What fails in plug-ins/common? Is it win32 specific code? Nothing in that dir fails to build on Linux. Paste the compile log for this too. IIRC, only the jpeg plugin, due to lcms-related issues. -- Jernej Simončič http://eternallybored.org/ There is an exception to all laws. -- Government's Law ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list You are probably right. I did a distclean and re compiled and did not see an issue with common - so sorry about that. As for win-snap, here is what I am getting: winsnap.c: At top level: winsnap.c:397:1: error: no previous prototype for 'setCaptureType' [-Werror=missing-prototypes] winsnap.c:642:1: error: no previous prototype for 'InitApplication' [-Werror=missing-prototypes] winsnap.c:690:1: error: no previous prototype for 'InitInstance' [-Werror=missing-prototypes] winsnap.c:717:1: error: no previous prototype for 'winsnapWinMain' [-Werror=missing-prototypes] cc1.exe: some warnings being treated as errors make[3]: *** [winsnap.o] Error 1 make[3]: Leaving directory `/usr/src/gimp/gimp-2.7.5/gimp-2.7.5/plug-ins/win-snap' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/usr/src/gimp/gimp-2.7.5/gimp-2.7.5/plug-ins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/usr/src/gimp/gimp-2.7.5/gimp-2.7.5' make: *** [all] Error 2 ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
[Gimp-developer] AMD Partnership for OpenCL in GEGL and GIMP
Hello everyone, I'm Victor Oliveira and I was the Google Summer of Code student who implemented OpenCL support to GEGL, Joao S. Bueno was my mentor in the project. My GSoC project was very interesting and there is a lot else to do in order to have good performance in GEGL with OpenCL. At the same time, I've been contacted by AMD and they are very interested in OpenCL adoption by the Open-Source community and want to help me to continue this project. So, I'll be continuing it as a contractor for AMD in the next few months. Of course, all code will be Open-Source. In fact, I've been developing it in my Gegl branch: http://git.gnome.org/browse/gegl/?h=gsoc2011-opencl-2 We intend to have it working for real by March at most. So what I'd like to know is if it's possible to include this Gegl in the next stable release of GIMP after that? Also, there would be a problem if I generate Windows and Linux builds and have them in GIMP site as some experimental download? Thanks a lot. Victor Oliveira ___ gimp-developer-list mailing list gimp-developer-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-developer-list
