Wang Mingyu
c7a4469acc
Changelog:
==========
### Changed
- 'DFLT_GVPRPATH', a '$PATH'-like variable that gvpr uses to locate
user-referenced files, is now computed at runtime instead of build time. This
removes a barrier to relocating a Graphviz installation from one directory to
another.
- In the CMake build system, whether GDK-dependent components are built or not
can now be controlled by the '-DWITH_GDK={AUTO|ON|OFF}' option. #2714
### Fixed
- Gvedit and Smyrna on MinGW can now correctly locate their supporting runtime
data directories.
- The gvpr options '-v' for printing verbose messages is documented. This has
been supported since Graphviz 2.30 but undocumented.
- When using the CMake build system, 'DFLT_GVPRPATH' is no longer incorrectly
missing a ".:" prefix.
- On macOS, processing graphs involving URLs with the Quartz plugin is once
again possible. Previously this would crash. This was a regression in Graphviz
13.0.1. #2712
- In gvpr, updating a map or deleting items from the map no longer triggers a
use-after-free.
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe
This layer depends on:
URI: git://github.com/openembedded/openembedded-core.git branch: master
luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below
pacman -S lib32-gcc-libs lib32-glibc
Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386
Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' in the subject'
When sending single patches, please use something like: 'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix="meta-oe][PATCH"'
You are encouraged to fork the mirror on GitHub https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch.
Note, it is discouraged to send patches via GitHub pull request system. Such patches get less attention from developers and can be mishandled or not reviewed properly. Please use emails instead. For exemple, you can use 'git request-pull' to generate an email referencing your git repository.
Other services like GitLab, repo.or.cz or self-hosted setups are of course accepted as well, 'git fetch ' works the same on all of them. We recommend GitHub because it is free, easy to use, has been proven to be reliable and has a really good web GUI.
layer maintainer: Khem Raj raj.khem@gmail.com