BorlandTalk.com Forum Index BorlandTalk.com
Borland discussion newsgroups
 
Archives   FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Howto restrain library path from getting too long?

 
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (IDE)
View previous topic :: View next topic  
Author Message
Mika Torhola mika.torhola
Guest





PostPosted: Thu Jul 14, 2005 9:28 am    Post subject: Howto restrain library path from getting too long? Reply with quote




We have a fairly large project with dozens of forms.
Most of the forms belong to different components, and
therefore reside in different directories.

Recently - after adding one more form into the project -
we ran into a problem that caused C++ Builder to crash
completely during linking phase of our SW. The crash was
repeatable, and was caused by too long library path
approximately 3000 - 4000 characters). When we removed
one form (and one directory from the library path) from
the project, it compiled just fine.

Is it possible to somehow add forms to a project without
lengthening the library path?

I tried creating a static library that contains a form,
but that library won't link unless the form's directory
is added to the library path in the main project that
contains the library. If the directory is missing in the
library path, I'll just get "[Linker Error] Unable to open
file 'UMYFORM.DFM'".

--
MikaT

P.S.: We have applied the C++ Builder update #4,
but to no prevail.


Back to top
Mika Torhola
Guest





PostPosted: Fri Jul 15, 2005 6:53 am    Post subject: Re: Howto restrain library path from getting too long? Reply with quote



....forgot to say it in the previous post, but we're
using Borland C++ Builder 6.0 Professional.

--
MikaT


Back to top
Michael Gillen
Guest





PostPosted: Tue Jul 19, 2005 2:42 pm    Post subject: Re: Howto restrain library path from getting too long? Reply with quote



Mika Torhola wrote:

Quote:
...forgot to say it in the previous post, but we're
using Borland C++ Builder 6.0 Professional.

First, and least important, I install CBuilder in a directory Devtools. So I have an initial base
path of C:DevToolsCBuilder6
Second, I put all 3rd party libraries and components in C:Libs....
Third, subst an S: drive to my Source Code directory.

--
-Michael Gillen

Back to top
Mika Torhola
Guest





PostPosted: Wed Jul 20, 2005 7:15 am    Post subject: Re: Howto restrain library path from getting too long? Reply with quote

Thanks for good tips, especially the last one.
However, that only postpones the inevitable.

I guess then there's no way to link a dfm-file to a static
library in such a way, that the project using the library
wouldn't have to be aware of the dfm-file's location.

--
MikaT



"Michael Gillen" <michael (AT) gillenconsultinggroup-nospam (DOT) com> wrote

Quote:
Mika Torhola wrote:

...forgot to say it in the previous post, but we're
using Borland C++ Builder 6.0 Professional.

First, and least important, I install CBuilder in a directory Devtools. So I have an initial base
path of C:DevToolsCBuilder6
Second, I put all 3rd party libraries and components in C:Libs....
Third, subst an S: drive to my Source Code directory.

--
-Michael Gillen



Back to top
Mika Torhola
Guest





PostPosted: Wed Jul 20, 2005 7:34 am    Post subject: Re: Howto restrain library path from getting too long? Reply with quote

As a matter of fact, these tips will be of no use to us
in most projects, since we use relative paths...

--
MikaT



"Mika Torhola" <mika.torhola (AT) cc (DOT) tut.fi> wrote

Quote:
Thanks for good tips, especially the last one.
However, that only postpones the inevitable.

I guess then there's no way to link a dfm-file to a static
library in such a way, that the project using the library
wouldn't have to be aware of the dfm-file's location.

--
MikaT



"Michael Gillen" <michael (AT) gillenconsultinggroup-nospam (DOT) com> wrote

Mika Torhola wrote:

...forgot to say it in the previous post, but we're
using Borland C++ Builder 6.0 Professional.

First, and least important, I install CBuilder in a directory Devtools. So I have an initial base
path of C:DevToolsCBuilder6
Second, I put all 3rd party libraries and components in C:Libs....
Third, subst an S: drive to my Source Code directory.

--
-Michael Gillen





Back to top
Michael Gillen
Guest





PostPosted: Wed Jul 20, 2005 2:12 pm    Post subject: Re: Howto restrain library path from getting too long? Reply with quote

Mika Torhola wrote:

Quote:
As a matter of fact, these tips will be of no use to us
in most projects, since we use relative paths...

That is unfortunate. I use the subst capability to be compatible across different systems where
the source code is actually on differet drives. I had considered using a different drive for my Lib
directory, but it has not been necessary.

--
-Michael Gillen

Back to top
Display posts from previous:   
Post new topic   Reply to topic    BorlandTalk.com Forum Index -> C++ Builder (IDE) All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2006 phpBB Group
SEO toolkit © 2004-2006 webmedic.