Sure. as I stated above, my build environment is mingw-gcc and I use msys as the backend if you will. All my libraries are built within this environment.

BTW, make install also does not put share correctly even if you manually specify the datadir.

I am surprised by these strange paths as well. I don't have this issue with Gimp for example which I also build.

I have never heard of btool till today.

BTW, is there already a 64-bit Windows build for Inkscape?

Thanks for your help!

Partha

On Sat, Sep 21, 2013 at 5:32 PM, Krzysztof Kosiñski <tweenk.pl@...972.....> wrote:

2013/9/21 Partha Bagchi <partha1b@...400...>:

> I am convinced the problem is with the path that Inkscape is seeing. When I
> divert all stdout to file, I see the following:
> ________________________being log_______________________
> ** (inkscape.exe:4148): CRITICAL **: Inkscape::XML::Document*
> sp_repr_read_file(const gchar*, const gchar*): assertion 'Inkscape::IO::f
> ile_test( filename, G_FILE_TEST_EXISTS )' failed
>
> ** (inkscape.exe:4148): WARNING **: Unable to read keys file
> I:\oss-dev\msys\opt\inkspace\bin\/opt/inkspace/share\share\keys\default.xm
> l
>
> ** (inkscape.exe:4148): WARNING **: Null pixbuf for 00000000037DFA60
> [I:\oss-dev\msys\opt\inkspace\bin\/opt/inkspace/share\share\icons\
> remove-color.png]

Can you describe in some more detail how you are building Inkscape?

The standard way to do it is to use btool. These strange paths, with
mixtures of Unix and Windows components, might be an artifact of using
Autotools within MSYS.

Regards, Krzysztof