On Wed, Sep 06, 2006 at 10:08:04AM +0200, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> On Tue, Sep 05, 2006 at 06:46:23PM +0200, Enrico Forestieri
> Enrico> wrote:
> >> Anyway, if you want to take into account that someone could
> >> ac
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> On Tue, Sep 05, 2006 at 06:46:23PM +0200, Enrico Forestieri
Enrico> wrote:
>> Anyway, if you want to take into account that someone could
>> actually cross-compile to mingw using cygwin, the attached patch
>> fixes this issue.
On Tue, Sep 05, 2006 at 06:46:23PM +0200, Enrico Forestieri wrote:
> Anyway, if you want to take into account that someone could actually
> cross-compile to mingw using cygwin, the attached patch fixes this issue.
No, please don't apply this patch as it would also affect a cygwin build.
Both $hos
On Tue, Sep 05, 2006 at 03:49:12PM +0200, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> I was already aware of the last two, but was missing
> Enrico> LYX_ABS_TOP_SRCDIR, which was being hardcoded in posix style
> Enrico> into package.C.
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> I was already aware of the last two, but was missing
Enrico> LYX_ABS_TOP_SRCDIR, which was being hardcoded in posix style
Enrico> into package.C. Once taken care of that (a simple call to
Enrico> cygpath in the configure scrip
On Tue, Sep 05, 2006 at 12:29:39PM +0200, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> Look at package.C.in:
>
> Enrico> This is not going to work when packaging is windows or
> Enrico> macosx...
>
> Hmm, what is not going to work? th
On Mon, Sep 04, 2006 at 11:08:31AM +0200, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> IIRC, the build_support dir is not correctly spotted in a
> Enrico> native Windows build. Run "lyx -dbg init" to check it.
>
> It would be nice to i
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> Look at package.C.in:
Enrico> This is not going to work when packaging is windows or
Enrico> macosx...
Hmm, what is not going to work? the build support dir is BINDIR/../lib
always, isn't it?
But I do not think this is the
On Mon, Sep 04, 2006 at 04:16:28PM +0200, Georg Baum wrote:
> Bo Peng wrote:
>
> >> When LyX is run in place, lyx2lyx_version.py should be found in the
> >> build_support dir. IIRC, the build_support dir is not correctly spotted
> >> in a native Windows build. Run "lyx -dbg init" to check it.
> >
Bo Peng wrote:
>> When LyX is run in place, lyx2lyx_version.py should be found in the
>> build_support dir. IIRC, the build_support dir is not correctly spotted
>> in a native Windows build. Run "lyx -dbg init" to check it.
>
> I am not quite sure how autotools handle lyx2lyx_version.py but for
>
On Mon, Sep 04, 2006 at 11:08:31AM +0200, Jean-Marc Lasgouttes wrote:
> > "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
>
> Enrico> IIRC, the build_support dir is not correctly spotted in a
> Enrico> native Windows build. Run "lyx -dbg init" to check it.
>
> It would be nice to i
On Sun, Sep 03, 2006 at 11:05:53PM -0500, Bo Peng wrote:
> > When using autotools lyx2lyx_version.py is generated in lib/lyx2lyx
> > under the build directory. If you run lyx in place, this directory
> > is also taken into account and thus lyx2lyx_version.py is found:
>
> I agree that this is con
> "Enrico" == Enrico Forestieri <[EMAIL PROTECTED]> writes:
Enrico> IIRC, the build_support dir is not correctly spotted in a
Enrico> native Windows build. Run "lyx -dbg init" to check it.
It would be nice to investigate this.
JMarc
Bo Peng wrote:
When using autotools lyx2lyx_version.py is generated in lib/lyx2lyx
under the build directory. If you run lyx in place, this directory
is also taken into account and thus lyx2lyx_version.py is found:
I agree that this is convenient, but it is against the idea of
source/build sepa
When using autotools lyx2lyx_version.py is generated in lib/lyx2lyx
under the build directory. If you run lyx in place, this directory
is also taken into account and thus lyx2lyx_version.py is found:
I agree that this is convenient, but it is against the idea of
source/build separation. Right no
On Sun, Sep 03, 2006 at 09:25:48PM -0500, Bo Peng wrote:
> > When LyX is run in place, lyx2lyx_version.py should be found in the
> > build_support dir. IIRC, the build_support dir is not correctly spotted
> > in a native Windows build. Run "lyx -dbg init" to check it.
>
> I am not quite sure how
When LyX is run in place, lyx2lyx_version.py should be found in the
build_support dir. IIRC, the build_support dir is not correctly spotted
in a native Windows build. Run "lyx -dbg init" to check it.
I am not quite sure how autotools handle lyx2lyx_version.py but for
scons, it is generated from
On Sun, Sep 03, 2006 at 06:49:34PM +0100, José Matos wrote:
> On Sunday 03 September 2006 10:28, Abdelrazak Younes wrote:
> > So this means that neither scons nor autotools will work exclusively
> > with trunk/lib? I mean without a "make install"?
>
> They do, but I had not explored how they do
Bo Peng wrote:
If I understand correctly Andre and Georg report it seems that they do
not...
I run 'scons install' instead of 'scons lyx' or 'scons all' to test
lyx. This is safer although you can run scons install once to get the
lib files in place, and then 'scons lyx' to build lyx later.
W
If I understand correctly Andre and Georg report it seems that they do
not...
I run 'scons install' instead of 'scons lyx' or 'scons all' to test
lyx. This is safer although you can run scons install once to get the
lib files in place, and then 'scons lyx' to build lyx later.
Note that scons in
José Matos wrote:
On Sunday 03 September 2006 10:28, Abdelrazak Younes wrote:
So this means that neither scons nor autotools will work exclusively
with trunk/lib? I mean without a "make install"?
They do, but I had not explored how they do it. :-)
If I understand correctly Andre and Georg
On Sunday 03 September 2006 10:28, Abdelrazak Younes wrote:
> So this means that neither scons nor autotools will work exclusively
> with trunk/lib? I mean without a "make install"?
They do, but I had not explored how they do it. :-)
--
José Abílio
José Matos wrote:
On Saturday 02 September 2006 09:07, Abdelrazak Younes wrote:
ImportError: No module named lyx2lyx_version
This is with a CMake build, so maybe this explains that. Peter, any clue?
There is a file lyx2lyx_version.py.in that is converted with both autotools
and scons. The
On Saturday 02 September 2006 09:07, Abdelrazak Younes wrote:
> ImportError: No module named lyx2lyx_version
>
> This is with a CMake build, so maybe this explains that. Peter, any clue?
There is a file lyx2lyx_version.py.in that is converted with both autotools
and scons. The resulting file is
Hello Jose,
I cannot open an old format file anymore:
Traceback (most recent call last):
File "d:/devel/lyx/trunk/lib/lyx2lyx/lyx2lyx", line 21, in ?
import LyX
File "d:\devel\lyx\trunk\lib\lyx2lyx\LyX.py", line 28, in ?
import lyx2lyx_version
ImportError: No module named lyx2lyx_ver
25 matches
Mail list logo
