X-Git-Url: https://git.saurik.com/wxWidgets.git/blobdiff_plain/6955ce29ed8995e4407feb2c9259fbece398ff2a..50a8b42c51d376a882c8f8ddd28457c18f0e48f1:/docs/readme_vms.txt diff --git a/docs/readme_vms.txt b/docs/readme_vms.txt index 734ffa73f9..c44a38a7f1 100644 --- a/docs/readme_vms.txt +++ b/docs/readme_vms.txt @@ -9,7 +9,7 @@ The compilation was tested with -GTK1.2.8 (for wxGTK) To get everything compiled you'll need to have installed prior to compiling -wxWindows: +wxWidgets: -Bison get it from http://www.openvms.digital.com/freeware/ You' have to fix the following bug: @@ -67,7 +67,7 @@ File $DISK2:[JOUKJ.PUBLIC.TIFF.TIFF.LIBTIFF]TIFFCOMP.H;1 ( from http://www.openvms.digital.com/openvms/products/ips/gtk.html ) -Redefine the logical SYS$LIBRARY in such a way that it also points - to the includefile/library directories of the obove packages: + to the includefile/library directories of the above packages: i.e. $ define sys$library sys$sysroot:[syslib],- $disk2:[joukj.public.xpm.xpm.lib],- @@ -102,25 +102,25 @@ $ ass $disk2:[joukj.public.gtk.gtk.glib],- versions of VMS. If you get lib$get_current_invo_context undefined while linking you'll have to add "lib$get_current_invo_context"="LIB$GET_CURR_INVO_CONTEXT" - in [.src.unix]descrip.mms to CXX_DEFINE. and recompile wxWindows. + in [.src.unix]descrip.mms to CXX_DEFINE. and recompile wxWidgets. -Some versions of the CC compiler give warnings like %CC-W-CXXKEYWORD, "bool" is a keyword in C++ .... when compiling if You encounter these, replace mms by mms/ignore=warning in the following - -Now build evrything using one of the following + -Now build everything using one of the following mms mms gtk mms motif in the main directory of the distribution. Without an argument both wxGTK - and wxMOTIF are build. The libraies are build in the [.lib] directory. - All the samples I tried are build automatically. + and wxMOTIF are built. The libraries are built in the [.lib] directory. + All the samples I tried are built automatically. -I think in general wxGTK is better maintained, so that version is my first choice. - -Note that only a few people have used wxWindows on VMS so many problems are + -Note that only a few people have used wxWidgets on VMS so many problems are to be expected.