Matěj Týč wrote: > > On unixes, wxWidgets will install their wx-config script to <prefix>/bin > Since it would be overwritten by another wxWidgets library, it is > obviously good to > change the prefix. > You can install debug, release, unicode versions of wxWidgest all in the same place. And still the wx-config will find all of them correctly. Library names are all named differently. And includes are general for all flavors.
> Build tools usually allow specifying path to one of those wx-config. > That is oke. The one found in the path is used. > Also notice that if two libraries are installed with the same prefix, > their headers are overwritten. Even this may become a problem. > With wxWidgest there is no problem. But still having a prefix is nice, in case one wants to use it. > I understand that. However, autotools are much better everywhere else except > Windows and wxWidgets themselves use autotools (=configure) to certain extent. > The current build system is quite complicated and somewhat broken, if > it stays like > that, wxart probably won't make it into Linux distributions. > I understand that Cmake is good since it enables both IDE use and > portability, but it also has its toll - it is not really simpler nor > more elegant than others and not very convenient to the end user > either. > We (Francesco) tried to use bakefile a year or two ago. Like in wxWidgets and wxLua. It generated all the makefiles and project files as part of the distribution. But support and maintenance was a problem. Eventually we removed it. Cmake has the advantage that it is well supported and documented, and has a large user/developer group. Even KDE is using it now. And most important can maintain it since it its not that complicated. Bakefiles would take far to much time for me to understand and maintain. For the time being it will be Cmake, and can be improved where needed. > > on Unixes, it is usually like that: > Binaries (in this case probably only the configure program) should go > into <prefix>/bin > Oke. > Libraries into <prefix>/lib, or into subdirectories (not common if > they are not loadable modules) > Include files into <prefix>/include, they end up in additional subdirs > quite often. > I hope those are oke, but will test it. > Other files can go into <prefix>/share/wxart2d. > Don't understand why this is called share, but oke with me. > There is even an optional standard what to put where: > http://www.gnu.org/prep/standards/standards.html#Directory-Variables > Thanks. > > Robopro looks really great. Is there some tutorial or quickstart how > to make and manage a simple diagram? The 'wires' sample is quite > complex... > No, and wxart2d is not easy. Maybe the next is easier to use. wxShapeFramework http://sourceforge.net/project/shownotes.php?release_id=651005 ------------------------------------------------------------------------------ _______________________________________________ Wxart2d-users_dev mailing list Wxart2d-users_dev@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wxart2d-users_dev
