As a workaround you can try to delete " CMakeCache.txt" as well as the folder " CMakeFiles".
This fixed a sigc++ error for me last time. Obviously there's something strange going on, though, so the cmake guys should really look into it...
Regards, Eduard
Am 2. Oktober 2016 12:08:50 nachm. schrieb Adrian Boguszewski <adrbogus1@...3350...>:
This segfault is really weird, because in line 1444 there is no file loading.
I've done everything from http://wiki.inkscape.org/wiki/ index.php/Compiling_Inkscape_on_Windows_64-bit, but when I type
cmake -G "MinGW Makefiles" ..
pkg_config can't find sigc++2.0.
Best regards, Adrian
On 1 October 2016 at 20:03, Yale Zhang <yzhang1985@...400...> wrote:
I'm a Windows 10 user (think you have to be if you're using the latest Wacom hardware).
I was able to build only after adding -DLIBXMLPP_BUILD to CMAKE_CXX_FLAGS. Without it, I got lots of refrences to symbols that start with __imp which means Windows DLL functions, while you're building libxml++ statically.
I was going to try it and see how much faster my massive SVGs load, but it crashed:
Program received signal SIGSEGV, Segmentation fault. Inkscape::Application::get_all_desktops (this=0xfb45b10, listbuf=...) at /home/yale/sax-parser/src/inkscape.cpp:1444 1444 /home/yale/sax-parser/src/inkscape.cpp: No such file or directory. (gdb) where #0 Inkscape::Application::get_all_desktops (this=0xfb45b10, listbuf=...) at /home/yale/sax-parser/src/inkscape.cpp:1444 #1 0x0000000064344de8 in Inkscape::CmdLineAction::idle () at /home/yale/sax-parser/src/main-cmdlineact.cpp:83 #2 0x0000000002566113 in operator() (this=<optimized out>) at /opt/gcc6.2-mingw64/x86_64-w64-mingw32/include/sigc++-2.0/ sigc++/functors/slot.h:447 #3 (anonymous namespace)::glibmm_main_context_invoke_callback (data=<optimized out>) at main.cc:330 #4 0x0000000002021e3e in g_main_dispatch (context=0xd947850) at gmain.c:3154 #5 g_main_context_dispatch (context=context@...3051...=0xd947850) at gmain.c:3769 #6 0x0000000002022168 in g_main_context_iterate (context=0xd947850, block=block@...3051...=1, dispatch=dispatch@...3051...=1, self=<optimized out>) at gmain.c:3840 #7 0x00000000020225d3 in g_main_loop_run (loop=0xfb76a00) at gmain.c:4034 #8 0x0000000002fe815d in gtk_main () at gtkmain.c:1269 #9 0x0000000000405a68 in sp_main_gui(int, char const**) () #10 0x0000000005de1080 in Gtk::Window::window_class_ () from C:\Users\Yale\inkscape.gmesh\libgtkmm-3.0-1.dll #11 0x000000000d8bb970 in ?? () #12 0x000000000d898efb in ?? () #13 0x000000000d8c2220 in ?? () #14 0x0000000010232f10 in ?? () #15 0x0000000000000000 in ?? ()
Why can't you build it on Windows? I use a MingW 64 cross compiler setup. -Yale
On Sat, Oct 1, 2016 at 4:45 AM, Adrian Boguszewski <adrbogus1@...3350...> wrote:
Hi there,
I finished sax parser project and I need to test it on Windows. Unfortunately I can't compile it. Is anybody here, who builds Inkscape on Windows and could check my changes, especially loading different file
types?
To detect file type I use a mime type of file from Gio library. I want to know if the content type is the same as on linux. Precisely: "image/svg+xml", "application/xml" or "text/html" for uncompressed svg,
xml
and html files and "image/svg+xml-compressed", "application/x-gzip" for svgz.
Compiling, running and opening different files is sufficient to know that everything is ok. If there are no warnings of course.
Branch to compile: https://code.launchpad.net/~adrianboguszewski/inkscape/sax-parser
Thanks!
Best regards, Adrian
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel
Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
Inkscape-devel mailing list Inkscape-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel