w32 cygwin, php and openjade issues

From: Date: Sun, 19 Sep 2004 19:09:17 +0000
Subject: w32 cygwin, php and openjade issues
Groups: php.doc 
Request: Send a blank email to phpdoc+get-969364176@lists.php.net to get a copy of this message
Hello, phpdoc@lists.php.net There are some problems with using openjade from cygwin package on windows and native w32 PHP binary. ./configure script uses PHP version to determine full working path, used in file-entities.php and later in entities/file-entities.ent If PHP is compiled with cygwin, path should be prefixed with /cygdrive/, in this case openjade.exe in ../php-tools will not understand these paths. Also if openjade is from cygwin and PHP binary is from standard win32 distrubutive, paths produced by scripts/file-entities.php (i.e. c:/...) will be not understandable by openjade, so.. Is it really necessary to have absolute paths in entities/file-entities.ent? There's a comment indicating, that absolute paths are keeped to have meaningful error messages. Is there any other reasons? If there isn't - how about to use relative paths in entities/file-entities.ent? ----[file-entities.php.in]--- ... // when php complied on cygwin, the working path have to be /cygdrive.. // the below preg_replace have to be done only using binary php complied on MSVC. // let's find if php was complied by cygwin: $cygwin_complied = eregi("CYGWIN",php_uname()) ? true : false; // The output directory, which we need to parse for windows specific // things, and correct all problems is needed. // Also use absolute path to have meaningful error messages $out_dir = abs_path(strip_cygdrive("@WORKDIR@")); // this path if used for saving the ent file: $script_out_dir = $cygwin_complied ? "@WORKDIR@" : $out_dir; ... ----------------------------- t -- --[ http://wiki.phpdoc.info/DocLinks ]--

« previous php.doc (#969364176) next »