Kayvan A. Sylvan wrote:
> Hi Angus,
>
> Something in the latest patches broke the path finding code again on
> Cygwin. I am using the latest lyx-devel CVS.
>
> [EMAIL PROTECTED] ~/src/tex/lyx/resume] lyx resume.lyx
> Unable to determine the path to the LyX binary from the command line
> ly
On Mon, Jan 31, 2005 at 07:47:56PM +, Angus Leeming wrote:
>
> See Lars' "Kill FileInfo" patch and my comment to it.
> http://article.gmane.org/gmane.editors.lyx.devel:41332
> http://article.gmane.org/gmane.editors.lyx.devel:41350
>
lars> - got rid of IsFileWriteable
lars> - got rid of Delet
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| On Mon, Jan 31, 2005 at 07:47:56PM +, Angus Leeming wrote:
>>
>> See Lars' "Kill FileInfo" patch and my comment to it.
>> http://article.gmane.org/gmane.editors.lyx.devel:41332
>> http://article.gmane.org/gmane.editors.lyx.devel:41350
>>
>
| l
On Mon, Jan 31, 2005 at 10:50:45PM +0100, Lars Gullik Bjønnes wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
>
> | On Mon, Jan 31, 2005 at 07:47:56PM +, Angus Leeming wrote:
> >>
> >> See Lars' "Kill FileInfo" patch and my comment to it.
> >> http://article.gmane.org/gmane.editors.ly
Kayvan A. Sylvan wrote:
>> I need a super detailed bug report.
>> Without it I have no clue what goes wrong...
>> (for all I know it is a couple of string() that should be native() )
>
> Latest Cygwin, latest CVS build:
>
> $ ./src/lyx
> Unable to determine the path to the LyX binary from the
On Mon, Jan 31, 2005 at 10:50:18PM +, Angus Leeming wrote:
> Kayvan, you're running with LyX in-place, right?
No. In place or installed, I get identical results.
> Could you add a few print statements in src/support/packages.C.in ?
Sure. What kind? Where?
---Kayvan
-
I just tried compiling latest CVS again. Here is what happens:
g++ -DHAVE_CONFIG_H -I. -I../../../lyx/src/support -I../../src
-I../../../lyx/src/support/.. -I../../../lyx/boost -I/usr/local/include
-W -Wall -I/usr/X11R6/include -O2 -fno-exceptions -mms-bitfields
-MT fs_extras.lo -MD -MP -MF .deps/
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| I just tried compiling latest CVS again. Here is what happens:
>
| g++ -DHAVE_CONFIG_H -I. -I../../../lyx/src/support -I../../src
| -I../../../lyx/src/support/.. -I../../../lyx/boost -I/usr/local/include
| -W -Wall -I/usr/X11R6/include -O2 -fno-exce
On Tue, Feb 01, 2005 at 10:59:47AM +0100, Lars Gullik Bjønnes wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
>
> | I just tried compiling latest CVS again. Here is what happens:
> >
> | g++ -DHAVE_CONFIG_H -I. -I../../../lyx/src/support -I../../src
> | -I../../../lyx/src/support/.. -I../.
Kayvan A. Sylvan wrote:
> Index: src/support/fs_extras.C
> ===
> RCS file: /cvs/lyx/lyx-devel/src/support/fs_extras.C,v
> retrieving revision 1.2
> diff -u -r1.2 fs_extras.C
> --- src/support/fs_extras.C 2005/01/31 19:31:11 1.2
Angus Leeming <[EMAIL PROTECTED]> writes:
| I'm about to commit the equivalent:
>
| @@ -22,6 +22,11 @@
| # endif
| # endif
>
| +#if defined (BOOST_WINDOWS)
| +# define WIN32_LEAN_AND_MEAN
| +# include
| +#endif
If that is what is used in boost them ok. Else please use the same as
boost uses.
Lars Gullik Bjønnes wrote:
> | +#if defined (BOOST_WINDOWS)
> | +# define WIN32_LEAN_AND_MEAN
> | +# include
> | +#endif
>
> If that is what is used in boost them ok. Else please use the same as
> boost uses.
Lars, get a grip please. Your commit was broken. It now works. The code is
clean. So w
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | +#if defined (BOOST_WINDOWS)
>> | +# define WIN32_LEAN_AND_MEAN
>> | +# include
>> | +#endif
>>
>> If that is what is used in boost them ok. Else please use the same as
>> boost uses.
>
| Lars, get a grip please. Your co
On Tue, Feb 01, 2005 at 04:53:50PM +, Angus Leeming wrote:
> Lars Gullik Bjønnes wrote:
> > | +#if defined (BOOST_WINDOWS)
> > | +# define WIN32_LEAN_AND_MEAN
> > | +# include
> > | +#endif
> >
> > If that is what is used in boost them ok. Else please use the same as
> > boost uses.
>
> Lars
Lars Gullik Bjønnes wrote:
> | Lars Gullik Bjønnes wrote:
>>> | +#if defined (BOOST_WINDOWS)
>>> | +# define WIN32_LEAN_AND_MEAN
>>> | +# include
>>> | +#endif
>>>
>>> If that is what is used in boost them ok. Else please use the same as
>>> boost uses.
>>
> | Lars, get a grip please. Your commit
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| Regardless of whether it is run in place or installed, I get the same
| message:
>
| "Unable to determine the path to the LyX binary from the command line [...]"
>
| If I give the full path to the binary, then I get:
>
| "Unable to determine the sys
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | Lars Gullik Bjønnes wrote:
| +#if defined (BOOST_WINDOWS)
| +# define WIN32_LEAN_AND_MEAN
| +# include
| +#endif
If that is what is used in boost them ok. Else please use the same as
bo
Lars Gullik Bjønnes wrote:
> | Either the above enables the file to compile or it doesn't, no? Not
> | even Windows would use WIN32_LEAN_AND_MEAN to change the meaning of
> | DWORD. It exists solely to enable the developer to not drag in every
> | single header file in the entire machine. What's th
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | Either the above enables the file to compile or it doesn't, no? Not
>> | even Windows would use WIN32_LEAN_AND_MEAN to change the meaning of
>> | DWORD. It exists solely to enable the developer to not drag in every
>> | si
On Tue, Feb 01, 2005 at 07:08:14PM +0100, Lars Gullik Bjønnes wrote:
>
> boost/libs/filesystem/src:
> exception.cpp
> operations_posix_windows.cpp
> path_posix_windows.cpp
>
> Actually... easy solution... make sure that BOOST_POSIX is defined.
> f.ex in our config.h.
>
> put
>
> #define BOOST_P
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| On Tue, Feb 01, 2005 at 07:08:14PM +0100, Lars Gullik Bjønnes wrote:
>>
>> boost/libs/filesystem/src:
>> exception.cpp
>> operations_posix_windows.cpp
>> path_posix_windows.cpp
>>
>> Actually... easy solution... make sure that BOOST_POSIX is defin
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
| Then we have to decide on the best way to handle this.
>
| If we just make BOOST_POSIX be set for cygwin, then it works for you.
| But for the next guy using cygwin it will break.
>
| So are there any kindo of configure tests we can use to discov
On Wed, Feb 02, 2005 at 08:23:00AM +0100, Lars Gullik Bjønnes wrote:
> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>
> >
> | Then we have to decide on the best way to handle this.
> >
> | If we just make BOOST_POSIX be set for cygwin, then it works for you.
> | But for the next guy using cygwi
"Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
| On Wed, Feb 02, 2005 at 08:23:00AM +0100, Lars Gullik Bjønnes wrote:
>> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
>>
>> >
>> | Then we have to decide on the best way to handle this.
>> >
>> | If we just make BOOST_POSIX be set for cygwin, the
On Wed, Feb 02, 2005 at 08:30:25AM +0100, Lars Gullik Bjønnes wrote:
> "Kayvan A. Sylvan" <[EMAIL PROTECTED]> writes:
>
> | On Wed, Feb 02, 2005 at 08:23:00AM +0100, Lars Gullik Bjønnes wrote:
> >> [EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
> >>
> >> >
> >> | Then we have to decide on the be
L>>> #define BOOST_POSIX 1
>>
> | Yes, this works.
>
> Ok.
>
> Then we have to decide on the best way to handle this.
>
> If we just make BOOST_POSIX be set for cygwin, then it works for you.
> But for the next guy using cygwin it will break.
No, I don't think so. All our file names currently g
Angus Leeming <[EMAIL PROTECTED]> writes:
| L>>> #define BOOST_POSIX 1
>>>
>> | Yes, this works.
>>
>> Ok.
>>
>> Then we have to decide on the best way to handle this.
>>
>> If we just make BOOST_POSIX be set for cygwin, then it works for you.
>> But for the next guy using cygwin it will break.
Lars Gullik Bjønnes wrote:
> | L>>> #define BOOST_POSIX 1
>>> | Yes, this works.
>>>
>>> Ok.
>>>
>>> Then we have to decide on the best way to handle this.
>>>
>>> If we just make BOOST_POSIX be set for cygwin, then it works for you.
>>> But for the next guy using cygwin it will break.
>>
>
On Wed, Feb 02, 2005 at 09:55:53AM +, Angus Leeming wrote:
> to constuct these paths because, as we've just found out, Boost.Filesystem
> expects a particular OS to use either Windows or Posix-style paths and
> Cygwin can use BOTH.
... even within the same file name. I.e. 'C:Programs\LyX/lib'
29 matches
Mail list logo
