Target path length

From: Thomas Witt (witt_at_[hidden])
Date: 2002-06-15 12:30:24

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I just spend the better part of today chasing a bug that turned out to be a 
problem with target path length.

Currently all features have long speaking names that are easy to read and 
remember. So far so good. As a result the target path get quite long as well. 
This is especially a problem with the stlport toolsets.

What happened to me was that I had a generated cpp file sitting in 
$(LOCATE_TARGET). This cpp file include a file from $(LOCATE_SOURCE), using 
"#include "relative-path-here". On W2k both cl and icl complained that they 
could not find the include file, when the target path exceeded a certain 
length. Yes I am quite certain that the problem is length and not depth.

It seems like path length is still an isssue on W2k, so my question is: 
Shouldn't we try to use shorter feature names to avoid these problems? E.g. 
stlport-iostreams -> stlp-ios and the like.

Comments?

Thomas

- -- 
Dipl.-Ing. Thomas Witt
Institut fuer Verkehrswesen, Eisenbahnbau und -betrieb, Universitaet Hannover
voice: [phone] - 4273, fax: [phone]
http://www.ive.uni-hannover.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE9C3m00ds/gS3XsBoRAh6nAJ9xDWCHMU88BvIiFtmbQ77cY50NvwCbB8LL
/AjH/ndZkr1MxhTCtJ9eV84=
=Ongf
-----END PGP SIGNATURE-----