Gotta try relative path too, I'm quite sure I tried to do that as well :)
On 1/29/08, Philip Jenvey <[EMAIL PROTECTED]> wrote:
>
>
> On Jan 28, 2008, at 4:07 AM, Mikael Lepistö wrote:
>
> > I tried this one already, it seemed to work only if the tookit dir is
> > under the pylons project tree like
On Jan 28, 2008, at 4:07 AM, Mikael Lepistö wrote:
> I tried this one already, it seemed to work only if the tookit dir is
> under the pylons project tree like this:
>
> myprojects/pylonsproject/
> myprojects/pylonsproject/pylonsproject
> myprojects/pylonsproject/toolkit
>
> situation that I wou
I tried this one already, it seemed to work only if the tookit dir is
under the pylons project tree like this:
myprojects/pylonsproject/
myprojects/pylonsproject/pylonsproject
myprojects/pylonsproject/toolkit
situation that I would like is:
myprojects/pylonsproject/
myprojects/pylonsproject/pylo
Mikael Lepistö wrote:
> Hi,
>
> We have a toolkit library that we use in many pylons projects and it
> is outside of normal pylons project tree. Now we have problem, that we
> cannot get setup tools to extract messages outside of our pylons
> source tree to get localization also for toolkit.
>
>
Hi,
We have a toolkit library that we use in many pylons projects and it
is outside of normal pylons project tree. Now we have problem, that we
cannot get setup tools to extract messages outside of our pylons
source tree to get localization also for toolkit.
our directory structure is basically
