On Wednesday 18 June 2003 15:05, Dave Page wrote: > Yes, you need the symlink. It's there to provide a consistent name for > the config script no matter what build options wx was compiled with. If > you want to run with a non-standard wx installation, or the non-default > build, perhaps you can persuade Adam to add --with-wx-config= option to > override the script name?
Yes, but the name of the wxGTK library can be guessed from these options: --enable-unicode => u --enable-debug => d /usr/bin/wxgtk2{u}{d}-2.5-config Users can be several wxGTK versions at once. One symlink cannot point to all version of wxGTK installed. For example, a user may need to install: - wxGTK 2.4 in shared mode, - wxGTK 2.5 cvs in shared mode with Unicode. A Symlink cannot be part of a wxGTK2.5 or a pgAdmin3 package. Or it would break existing wxGTK2.4 packages. Cheers, Jean-Michel ---------------------------(end of broadcast)--------------------------- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])