> let me emphasize that the layout of the entire "proj" directory will
> be consistent across all users and all machines since it will
> represent a single SVN checkout, so that's not an issue. of course,
> anyone will be free to check it out anywhere they want but once they
> do, its structure wi
On Wed, 17 Mar 2010, Bob McConnell wrote:
> I suspect you will have to manage that on a machine by machine
> basis, unless you can convince the entire development team to create
> a common directory structure that encompasses all projects.
i'm not sure what you mean by the above. while that si
On Wed, 17 Mar 2010, Bob McConnell wrote:
... snip ...
> IOW, you want to point into the first project's test directory from
> other projects when you can't know the relative paths between those
> projects?
>
> I suspect you will have to manage that on a machine by machine
> basis, unless you can
From: Robert P. J. Day
> On Tue, 16 Mar 2010, John Black wrote:
>> On 03/16/2010 06:57 PM, Robert P. J. Day wrote:
>> >i have a project (let's call it "proj") which lives in the
"proj"
>> > directory and which contains several subdirs, some of which might
>> > contain their own subdirs and so
On Tue, 16 Mar 2010, John Black wrote:
> On 03/16/2010 06:57 PM, Robert P. J. Day wrote:
> >i have a project (let's call it "proj") which lives in the "proj"
> > directory and which contains several subdirs, some of which might
> > contain their own subdirs and so on. some of those subdirs mi
On Tue, Mar 16, 2010 at 9:48 PM, Ryan Sun wrote:
> just utilize include_path directive in php.ini
yea, or via ini_set('include_path', );
--
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
On Tue, Mar 16, 2010 at 1:57 PM, Robert P. J. Day wrote:
>
> and all PHP scripts would start off with something like:
>
> set_include_path(get_include_path() . PATH_SEPARATOR . getenv('PROJ_DIR'));
>
just utilize include_path directive in php.ini
--
PHP General Mailing List (http://www.php.net/
On 03/16/2010 08:50 PM, John Black wrote:
So I just set $include = './include/abc/def/' at the top of the
correction, I set $include to the relative path of the include directory
and then use it like this:
$include = '../../include/';
require $include.'abc/file1.php';
require_once $include.
On 03/16/2010 06:57 PM, Robert P. J. Day wrote:
i have a project (let's call it "proj") which lives in the "proj"
directory and which contains several subdirs, some of which might
contain their own subdirs and so on. some of those subdirs might
contain utility classes that i want to include o
9 matches
Mail list logo
