Etox still failed to compile with the new cvs snapshot today... Did
anybody have the same problem?
And does anybody know why it's looking for config.h.in??
Cheers,
Didier.
On 08/05/04, at 17:23 +0800, Didier Casse <[EMAIL PROTECTED]>
wrote:
> Some help needed!
> I got some compilation errors
You're building Entice against the outdated Esmart in e17/proto/esmart.
Esmart has been moved to e17/libs/esmart and is now a collection of
libraries, rather than a single library. Did you get the memo about this?
--Ibukun
Jeremy Kolb wrote:
Now sure what do do here, but I made some fixes to g
Shish wrote:
1) Images and other binary stuff should be checked in (added) with
-kb for several reasons, this not being one of them.
I know -kb helps CVS figure out how to do some things, but what other
reasons are there, and why isn't binary file corruption one of them?
The -kb flag can be set o
> 1) Images and other binary stuff should be checked in (added) with -kb
> for several reasons, this not being one of them.
I know -kb helps CVS figure out how to do some things, but what other reasons
are there, and why isn't binary file corruption one of them?
> 2) When working with unix stuff
Shish wrote:
It seems that the images in CVS were checked in as plain unix text, so anyone
checking them out with the native windows client will have them corrupted by
being changed to windows' line endings. I got round this by checking out CVS
with -kb (force binary), but they should really be mar
It seems that the images in CVS were checked in as plain unix text, so anyone
checking them out with the native windows client will have them corrupted by
being changed to windows' line endings. I got round this by checking out CVS
with -kb (force binary), but they should really be marked as binary
