Hi.

G'MIC now uses a git repository in replacement of the old CVS one to manage its source code.
You can now have an anonymous access to this source repository, using git :



The CVS repo is thus discontinued and won't be updated anymore. I'll ask the Sourceforge admins to disable it if possible.

Please forget about the old CVS repo then

Cheers.

Cool; next time I try samj's environment, I'll try to use the git command and hopefully win7 won't have a coniption about that.

Thanks David.

I was able to download it with the command you show in SF page:

@Lylejk

Here is a script to compile the plugin from GIT (in the archive "compile_gmic_gimp_plugin_64_win.zip").
The instructions are at the beginning of the script.
I have attached a screenshot.

Trying the script now samj; took around a minute to download the files and now it's waiting in step 05/24 and suspect it will take some time now to actually compile the plugin. lol

Thanks again samj.

@Lylejk
Thank you for testing
It is true that we must be patient with this compilation

OK; compiled using your script samj and funny thing is the result is a megabyte smaller then when I compiled from the original source that I downloaded at sourceforge. It does work as far as I can tell; maybe some folk here can verify that this one works for them too. Still strange that the size is 1 megabyte smaller and it only took around 12 to 14 minutes to compile (faster then yesterday).

@Lylejk

I tested your compilation. Everything is perfect, the operation is fast

When I transferred the plugin to my regular 64-bit GIMP, I was missing some dlls like libjpeg-9.dll, but I just copied the dlls that were in the directory you set up with your script and voila; all's well. Also, the plugin does seem to run a little (perceived maybe by me; lol) faster then the other compile. Again, thanks a heap for all the help.

One other question; does your environment work for compile maze5? I know that maze5 used chiron or something like that as my memory serves me correctly so I'm not sure. Not even sure if I have a make file that can be used to compile this plugin. Anyway, just curious.

@Lylejk
maze5 :
To compile maze5 it is necessary to install software malfunctioning in Windows. I will perhaps try cross-compiling on Linux, it will be easier
You can test, things can be improved with time ...

I actually was able to compile maze5 in Linux a year or so ago samj (32-bit Ubuntu; have since hosed that VM and now occasion power up my 64-bit Ubuntu); Linux is so much friendlier with respect to compiling plugins that is for sure.

I'd like again to draw attention to the fact that the G'MIC plug-in for GIMP should not be linked with the libjpeg and libtiff libraries. I suggest you use the default Makefile provided in the git repository of G'MIC instead (file 'src/Makefile') : typing "make gimp" on the shell will compile the plug-in with the default options, i.e. the same used on all other configurations (and it works the same for linux, windows and macosx). That's the way the plug-in should be compiled.

Compiling the plug-in with the libjpeg and libtiff libraries linked adds maybe some features to the plug-in, but these features are useless (the plug-in does not need to do image I/O from files most of the time, and it already natively supports .cimgz, .png, .bmp, .ppm image formats, so .tiff and .jpeg are really useless). The GIMP API manages the transfer of image buffers between GIMP and G'MIC, so don't worry, all your jpg and tiff images can be processed by the plug-in without needs for libjpeg and libtiff in G'MIC.

But most of all :

- It adds useless complexity and risks of incompatibility as it requires additional .dll files (and we all know here that these .dll are often the cause of installation troubles, as other installed programs may provide different versions of these .dll). The trouble it can cause do not worth the useless features it adds.
- It potentially breaks the compatibility between different versions of the plug-in for different systems. All other builds of the plug-ins (for linux32,linux64,macosx,win32) do not use libtiff and libjpeg at all.

So, to me, it looks like a really a bad idea to make the plug-in depend of libjpeg and libtiff.
There is one standard Makefile provided in the official source repository of G'MIC, it should be used instead of typing some custom command lines that may be broken in next releases (while the Makefile will be updated in any way).

@Ronounours

If the DLL are not present (TIFF and JPEG) the plugin does not use them, it's that simple.
For the rest I do not agree with you.
I'll test your explanations on Linux and see if it really is a problem.

No, it's not that simple. When compiling the plug-in, you activate some specific functionalities in the plug-in, some pieces of code that are compiled while they should not be. It makes then plug-in binary a bit larger than expected, and most of all, it has some side effects on the way image I/o are working. Nothing really serious, but this is useless, and it changes the behaviour of the plug-in regarding other versions of the binary. This can cause eventually some troubles in the future with new filters added, for win64 users.

I wouldn't like much to see complaints of filters not working because *you* forced the use of these extra library during the compilation of the plug-in.