Personally, I think the wiki would probably be a better place for stuff like that than the repo (but it's not really my call what goes in the repo or not).

There's already a stub for compiling for/on windows: http://wiki.gimp.org/index.php/Hacking:Building/Windows If you'd like a wiki account, I'm told you should hop on IRC and bother either LightningIsMyName or Alexia_Death.

If you need any more help with cross compiling, feel free to ask. A few people, including myself, have up to date cross compiling environments working, and wouldn't mind helping you (or anyone) out if you run into any more problems.

-- drawoc

On Sun, Nov 11, 2012 at 9:22 PM, Jehan Pags wrote:

Hi,

I have tried native compilation (the GIT repo) in a Windows 7 VM; then I tried to cross-compile.
I finally managed to complete the GIMP cross-compilation! This email from the archive has been a great help by the way: https://mail.gnome.org/archives/gimp-developer-list/2012-May/msg00067.html

This kind of information should definitely be in a WINDOWS-DEV-README (or whatever you wish to call it) file in our repo! That would prevent potential developers to search for days on the web (and for myself in the future maybe, because I probably, and hopefully, won't cross-compile anything for quite some time).

Would it be ok to include such a file in devel-docs/ for instance? I can provide an updated version for this procedure.

Jehan

_______________________________________________ gimp-developer-list mailing list
gimp-developer-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-developer-list

On 12.11.12 at 05:25 AM Jehan Pags wrote in Gimp-developer:

Indeed I think it could be a little more centralized. Between developer.gimp.org , the wiki, what is in the repo, etc. I am a little lost and end up spending more time on search engines than in the doc. :-/

I agree and am under the impression that developer.gimp.org isn't much maintained anymore and some items have a duplicate counterpart in the wiki. How about merging it into the wiki? At least all development related stuff was then in one place and it would be easier to maintain.

What do you (the reader) think about it?

Kind regards,

Sven

On 12.11.12 at 05:25 AM Jehan Pags wrote: > Indeed I think it could be a little more centralized. Between > developer.gimp.org , the wiki, what is > in the repo, etc. I am a little lost and end up spending more > time on search engines than in the doc. :-/

I agree and just wrote a proposal in the gimp-web mailing list for this.

Kind regards,

Sven

On 11/11/2012 9:04 pm, scl wrote:

On 12.11.12 at 05:25 AM Jehan Pagès wrote in Gimp-developer:

Indeed I think it could be a little more centralized. Between developer.gimp.org , the wiki, what is in the
repo, etc. I am a little lost and end up spending more time on search
engines than in the doc. :-/

I agree and am under the impression that developer.gimp.org isn't much maintained anymore and some items have a duplicate counterpart in
the wiki. How about merging it into the wiki? At least all development
related stuff was then in one place and it would be easier to maintain.

What do you (the reader) think about it?

I think the more centralized for documentation, the better.

Kind regards,

Sven

_______________________________________________ gimp-web-list mailing list
gimp-web-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-web-list

On Mon, Nov 12, 2012 at 9:04 AM, scl wrote:

On 12.11.12 at 05:25 AM Jehan Pags wrote in Gimp-developer:

Indeed I think it could be a little more centralized. Between developer.gimp.org , the wiki, what is in the repo, etc. I am a little lost and end up spending more time on search engines than in the doc. :-/

I agree and am under the impression that developer.gimp.org isn't much maintained anymore and some items have a duplicate counterpart in the wiki. How about merging it into the wiki? At least all development related stuff was then in one place and it would be easier to maintain.

What do you (the reader) think about it?

There is API reference which is automatically generated from code, AFAIK. The rest could go to the wiki, indeed.

Alexandre Prokoudine http://libregraphicsworld.org

On Mon, Nov 12, 2012 at 5:05 AM, Alexandre Prokoudine < alexandre.prokoudine@gmail.com> wrote:

There is API reference which is automatically generated from code, AFAIK. The rest could go to the wiki, indeed.

Agreed, and the API docs reference can be linked in the wiki on the main page.

Sam Gleske