Re[2]: [PHP-DOC] cvs: phpdoc /howto tools.xml

2005-04-03 Thread anatoly techtonik
||*()*|| Hi, Gabor.

 nlopess   Sun Apr  3 12:36:54 2005 EDT
 
   Modified files:  
 /phpdoc/howto tools.xml 
   Log:
   just put the PHP directory in the path

GH So then the only remaining stuff out of installing cygwin, is getting 
GH jade/sp. It would definitely simpilfy the process, if this could be 
GH integrated into the cygwin setup :)

I'll quote my letter from 20th of September 2004 (yes - that old).

--*[cut]*--
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?
--*[cut]*--

Look here for the rest of the thread.
http://www.manucorp.com/archives/phpdoc/200409/msg00536.php


t
-- 


Re[2]: [PHP-DOC] cvs: phpdoc /howto tools.xml

2005-04-03 Thread anatoly techtonik
||*()*|| Hi, Gabor.

GH The file-entities.php script already distinguishes between the cygwin
GH and the windows compiled PHP, so if the cygwin PHP is used, cygwin path 
GH values are generated into the output (so that implies a cygwin installed 
GH openjade). It does not need to be relative. Even if a windows PHP is 
GH used, we can pass on a parameter to generate cygwin path values. Why is 
GH that a problem later on?

The problem is to autodetect which openjade version we use - cygwined
or not.
  

t
-- 


Re[2]: [PHP-DOC] cvs: phpdoc /howto tools.xml

2005-04-03 Thread anatoly techtonik
||*()*|| Hi, Gabor.

 GH The file-entities.php script already distinguishes between the cygwin
 GH and the windows compiled PHP, so if the cygwin PHP is used, cygwin path 
 GH values are generated into the output (so that implies a cygwin installed 
 GH openjade). It does not need to be relative. Even if a windows PHP is 
 GH used, we can pass on a parameter to generate cygwin path values. Why is 
 GH that a problem later on?
 
 The problem is to autodetect which openjade version we use - cygwined
 or not.

GH Why? In configure, you can do quite some iteresting checks :) If the 
GH ../phpdoc-tools/jade/jade.exe is used, it is not cygwin, otherwise it is.

It could work. Just don't forget about ../phpdoc-tools/openjade/openjade.exe =)

t
-- 


Re[2]: [PHP-DOC] cvs: phpdoc /howto tools.xml

2005-03-02 Thread anatoly techtonik
||*()*|| Hi, Gabor.

  para
   You need the same tools as on Linux. The very basic
   thing is a CVS client. You can find one simple command
 - line client here at the ulink url=url.cvs-win;CVSHome.org/ulink
 - Win32 download pool. We do not recommend GUI tools such
 - as WinCVS, because they can easily screw up the module
 - with files not intended to be there (eg. files with
 - uppercased names). The best is to use one command line
 - client, as this way you are in control.
 + line client here at the ulink url=url.cvs-win;CVSHome.org/ulink.
 + Although you can use GUI tools such as WinCVS or TortoiseCVS,
 + we provided instructions only for command line client in order
 + to keep this HOWTO short and simple.

GH This screw up thing is (was?) actually true, but I don't mind making the 
GH discription simpler...

Well, I created file LETTERS.BIG to test if WinCVS can skip this fact
completely, but it didn't. File was shown in WinCVS panel in all
uppers. I can't think out case when such files can screw up CVS.
Maybe this info is outdated - do you have any examples how to test
that?

 +  to Windows, which are not needed for phpdoc. To install
 +  minimal set of required packages select
 +  literalautoconf/literal and literalmake/literal
 +  along with components, which are selected in setup by 
 +  default. You may also want to add literalcvs/literal
 +  to the installation list if you don't have CVS client yet.
 +  Do not care about dependencies - they will be selected
 +  automatically.

GH Wow, the new versions check for dependencies automatically? That is great.

Me too thinks so. =)
I have a feeling that some sentences can be rephrased, but I can't
see the way. I'm not surprised, though. =)


t
--