- Inkscape Devel - Inkscape Mailman

CMake on win64
by Eduard Braun 29 May '16

29 May '16

Hi all, I just tried to do a cmake build on win64 and (what did I expect?) it didn't work... I followed the instructions at [1] but when linking libinkscape_base.dll I got the following errors: [ 99%] Linking CXX shared library ..\lib\libinkscape_base.dll CMakeFiles\inkscape_base.dir/objects.a(demangle.cpp.obj):demangle.cpp:(.text+0x278): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(xslt.cpp.obj):xslt.cpp:(.text+0x78b): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x2a): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x33): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x166): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x16f): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x38e3): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x38ed): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x3d19): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x3d23): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(script.cpp.obj):script.cpp:(.text+0x4998): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0xf21): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0xf82): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x1356): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x13e5): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x18c3): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(emf-inout.cpp.obj):emf-inout.cpp:(.text+0x1c04): more undefined references to `strdup' follow CMakeFiles\inkscape_base.dir/objects.a(print.cpp.obj):print.cpp:(.text+0x296): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(print.cpp.obj):print.cpp:(.text+0x707): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(ink-comboboxentry-action.cpp.obj):ink-comboboxentry-action.cpp:(.text+0x17): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(color-profile.cpp.obj):color-profile.cpp:(.text+0x2193): undefined reference to `read' CMakeFiles\inkscape_base.dir/objects.a(color-profile.cpp.obj):color-profile.cpp:(.text+0x21d3): undefined reference to `close' CMakeFiles\inkscape_base.dir/objects.a(inkscape.cpp.obj):inkscape.cpp:(.text+0xcfa): undefined reference to `unlink' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x1b8): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x348): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x359): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x4a2): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x1a7): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(prefix.cpp.obj):prefix.cpp:(.text+0x328): more undefined references to `strdup' follow CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0x13): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0x23): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xad): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xb9): undefined reference to `dup2' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xdd): undefined reference to `fileno' CMakeFiles\inkscape_base.dir/objects.a(winmain.cpp.obj):winmain.cpp:(.text+0xe9): undefined reference to `dup2' CMakeFiles\inkscape_base.dir/objects.a(sp-filter.cpp.obj):sp-filter.cpp:(.text+0x42f): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(sp-filter.cpp.obj):sp-filter.cpp:(.text+0x4e2): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(sp-offset.cpp.obj):sp-offset.cpp:(.text+0x238a): undefined reference to `strdup' CMakeFiles\inkscape_base.dir/objects.a(sp-offset.cpp.obj):sp-offset.cpp:(.text+0x29d7): undefined reference to `strdup' ../lib/lib2geom_LIB.a(bezier-clipping.cpp.obj):bezier-clipping.cpp:(.text.startup+0x6f): undefined reference to `nextafter' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vfprintf.o):mingw_vfprintf.c:(.text+0x11): undefined reference to `_lock_file' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vfprintf.o):mingw_vfprintf.c:(.text+0x33): undefined reference to `_unlock_file' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vprintf.o):mingw_vprintf.c:(.text+0x16): undefined reference to `_lock_file' E:/Temp/Inkscape/build/mingw64/bin/../lib/gcc/x86_64-w64-mingw32/5.3.0/../../../../x86_64-w64-mingw32/lib/../lib/libmingwex.a(lib64_libmingwex_a-mingw_vprintf.o):mingw_vprintf.c:(.text+0x44): undefined reference to `_unlock_file' collect2.exe: error: ld returned 1 exit status src\CMakeFiles\inkscape_base.dir\build.make:18858: recipe for target 'lib/libinkscape_base.dll' failed mingw32-make[2]: *** [lib/libinkscape_base.dll] Error 1 CMakeFiles\Makefile2:369: recipe for target 'src/CMakeFiles/inkscape_base.dir/all' failed mingw32-make[1]: *** [src/CMakeFiles/inkscape_base.dir/all] Error 2 Makefile:126: recipe for target 'all' failed mingw32-make: *** [all] Error 2 I assume there's an issue with linking to the standard library, but since I have no experience with CMake at all I don't have the slightest idea where to start... Anybody knows what might cause the issue and maybe even has a solution? Best Regards, Eduard [1] http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows_64-bi…

3 2

Releases Pages
by Martin Owens 26 May '16

26 May '16

Dear developers, I've released the next iteration of the website's "releases" app, this is the app that delivers each of our releases for different platforms. The releases app is still going through it's draft phase, but I hope to have the download pages replaced in time for 0.92. To do that I need your help to review the pages. If you can help with css patches, that would be great too. Currently available: https://inkscape.org/en/release/ Note: The releases will auto detect your os and give you the right download, but it's unconfigured on live and needs a bit of administrative help to get that all set up since the matching fields changed. I'd also like to draw your attention to the new request to donate after download: https://inkscape.org/en/release/0.91/windows/32-bit/ (click on one of the downloads to start) The text for these should be reviewed as well as the layout if you want to have a crack at the presentation. Thanks everyone for helping make 0.92 easier to deliver to our users. :-) Best Regards, Martin Owens

5 10

inkscape-0.92pre0 source tarball
by Bryce Harrington 26 May '16

26 May '16

Another pre-release is now available for testing from the source downloads page: https://inkscape.org/en/download/source/ The release is: 0.92pre1 Source Tarball Bzip https://inkscape.org/en/gallery/item/9633/inkscape-0.92pre1.tar.bz2 This is an early preview of our upcoming release and as such can be expected to have some stability issues or incomplete features. See Inkscape's bug tracker for a list of known issues. == Translation == We are now in String Freeze. All translators should strive to bring the language files up to date. Please aim to get all translation work committed by mid-June. == Packaging == Packagers for Linux, Windows, and OSX should use this source tarball for creating packages for their respective platforms. I strongly urge all packagers to test their packaging scripts at this time and generate packages for pre1. Please report to this thread with your status in getting the packages made, so I can identify where help is needed. Note that this was produced using the new cmake system, and the autoconfig build files are not included in this dist; if you require the autoconfig system for your platform you can still generate an autoconfig tarball from our VCS trunk, however you should prioritize shifting to cmake as we will be dropping autoconfig in the future 0.93 release. I plan to continue post further pre-releases on a roughly 1-2 week cadence until we feel the codebase is stable enough for the final release, which would be late June at the earliest. == About Screen == Hopefully a contest for the about screen should start up soonish? In the interim, and as a contingency in case it doesn't happen, could someone modify the 0.91 about screen to say 0.92pre? ------------------------------------------------------------------------ Thanks, Bryce

2 1

Inkscape todays Trunk refuses to launch on Kubuntu 14.04 and 16.04
by Ivan Louette 25 May '16

25 May '16

Inkscape todays Trunk refuses to launch on Kubuntu 14.04 and 16.04 After clicking on its icon it tries to launch but but after some seconds its icon disappears from Kubuntu's bar and nothing more happens on screen. ivan

5 9

New video three features.
by Jabiertxo Arraiza Cenoz 25 May '16

25 May '16

Hi, here are my last video. Is a kind of showcase of three features: * Eraser tool with no width now in trunk. * Randomize color extension now with a limit slider, also in trunk. * Optional auto fill Delaunay triangles with color and thin stroke in the same color. The code of this are in this bug:https://bugs.launchpad .net/inkscape/+bug/1553497 Anyway, there is better/faster ways to make Delaunay based in a image. So this is just a example. http://jabiertxof.marker.es/2016/03/no-width-eraser-mode-limit-random.h tml Cheers, Jabier.

3 2

0.92 release
by Alex Valavanis 24 May '16

24 May '16

Hi All, Just wondering if there are plans to freeze development yet? I think we're getting close to having a working CMake build... are there any "must have" features that are not yet fully implemented in 0.92, or can we push on with fixing-up the remaining bugs and releasing? I'm quite eager to make the switch to a hard C++11 requirement and default to Gtk+ 3, so the sooner we can get 0.92 out, the better :) Best wishes, Alex

11 21

Re: [Inkscape-devel] Tracking property value source
by Kamalpreet Grewal 23 May '16

23 May '16

Hi Tavmjong I have been looking at how the styles are written from the "style" attribute-value pairs in XML editor to the svg file when drawing is saved. It is done via sp_repr_css_write_string() in repr-css.cpp. On applying the extension, the block that is written has been implemented via merge_styles.py script (revision 13161). How is the script connected and extracting various style values from the XML editor and showing it up as a class? -- Kamalpreet Kaur Grewal Blog: http://kamalpreetgrewal.com/

1 0

Extensions question - changing user's selection
by Mark Schafer 23 May '16

23 May '16

Inkscape signals to an extension that the user has selected one or more items by passing an --id parameter to the new process running the extension. The inkex.py file looks for these and groups them under inkex.selected for easy retrieval. I want to change the user's selection in my extension (they pick one path, I want to add to that selection). I can see (thanks to perspective.py) how to tell a new inkscape process which items are selected and that it should work on. BUT I can't see how to signal back to the original inkscape my new set of selected paths. (I was hoping for a inkex.setselected() to match the inkex.getselected() ) How is it done, is there an example ?

1 1

New feature to eraser tool
by Jabiertxo Arraiza Cenoz 22 May '16

22 May '16

Hi to all. A new feature born in Hackfest 2016 thanks to the idea of Martin Owens to improve the eraser tool. This is a 0.93 feature. Here are the video: http://jabiertxof.marker.es/2016/05/new-eraser-mode -in-inkscape.html And here the branch: https://code.launchpad.net/~inkscape.dev/inkscape/clip_eraser Cheers and dance!

3 5

Re: [Inkscape-devel] Tracking property value source
by Kamalpreet Grewal 21 May '16

21 May '16

On Tue, May 3, 2016 at 4:24 PM, Tavmjong Bah <tavmjong@...8...> wrote: >> I have been seeing the current CSS support taking in consideration >> the >> process of tracking the source of the property value of each object >> property. >> >> We know the styles are added to 'style' attribute immediately on >> creation. Besides one can modify any attribute's value via the XML >> editor after altering the values in its right panel and clicking the >> 'Set' button. The modified value is saved and reflected in the >> drawing. And on opening the file in text editor, everything is >> alright. > > Correct > >> Next I merge the styles of the object via 'Stylesheet' in Extensions >> to a stylesheet, save it and open it in text editor, same attributes >> and values are saved in <style>.....</style> tags. > > Yes. > >> But now when I modify any attribute's value in XML editor, 'style' >> attribute and drawing are working right but the values are not >> updated >> in the stylesheet. Is this what I have to fix to track the source of >> values? > > Basically, yes. Relying on an extension to create and manage style > sheets is not a good idea. It is very limiting as to what can be done > and it requires manual intervention. The current implementation that writes styles to the saved svg file, is it all implemented in style-internal.h? Numerous flags have been used with different combinations. I have been able to understand a small portion of the workflow. It would be helpful if you point me in some direction so that I can proceed further quickly. -- Kamalpreet Kaur Grewal Blog: http://kamalpreetgrewal.com/

1 1