Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB Public Beta Tests » View Thread |
Messages 1 to 6 of 6 total |
Delphi & C++ in BDS 4.0 |
Sat, Jan 27 2007 7:58 PM | Permanent Link |
Michael Baytalsky | Hi Tim,
I have a question not directly related to EDB I noticed that you (as well as other vendors I guess) release separate downloads for Borland Developer Studio (Delphi) 2006 and Borland Developer Studio (C++) 2006. I've been working on adding support for C++ also and I've noticed that BDS doesn't seem to have separate settings for Delphi & C++. This suggests, that both packages (bpl) must have same name (actually be the same package) or otherwise you won't be able to work with both personalities, because if you install C++ package, then Delphi package won't load (will report that certain unit is already imported in another loaded package - C++ one) and visa versa. I'm not sure if I explained the problem, but it seems that Borland suggests that we have one [pre-build] package for both personalities and just provide additional lib, obj & hpp files for C++ and dcu dcp for Delphi. This will not allow users to open that package and rebuild it, though, because BDS doesn't have personality-neutral package format and at the same time they must have the same name... Should we store them in different folders? This all kind of strange to me... What do you think about this? Regards, Michael |
Sun, Jan 28 2007 10:31 AM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< I've been working on adding support for C++ also and I've noticed that BDS doesn't seem to have separate settings for Delphi & C++. This suggests, that both packages (bpl) must have same name (actually be the same package) or otherwise you won't be able to work with both personalities, because if you install C++ package, then Delphi package won't load (will report that certain unit is already imported in another loaded package - C++ one) and visa versa. I'm not sure if I explained the problem, but it seems that Borland suggests that we have one [pre-build] package for both personalities and just provide additional lib, obj & hpp files for C++ and dcu dcp for Delphi. This will not allow users to open that package and rebuild it, though, because BDS doesn't have personality-neutral package format and at the same time they must have the same name... Should we store them in different folders? >> You have to use the special command-line dcc32.exe compilation switch /JL to generate the C++ files from a Delphi package. Other than that, the build works exactly the same. We keep them separate just because we have always traditionally kept the two separate (C++ and Delphi). -- Tim Young Elevate Software www.elevatesoft.com |
Sun, Jan 28 2007 1:37 PM | Permanent Link |
Michael Baytalsky | Thanks, Tim! The switch information is useful, cause I couldn't find it in docs. However, this is not what I asked If you deploy 2 copies of BPL with different names, then people won't be able to install them both - because BDS uses same place to register them and so it will attempt to load them from both Delphi & C++ personalities. I'm talking about people who actually use both personalities of BDS (maybe in different projects). Regards, Michael Tim Young [Elevate Software] wrote: > Michael, > > << I've been working on adding support for C++ also and I've noticed that > BDS doesn't seem to have separate settings for Delphi & C++. This suggests, > that both packages (bpl) must have same name (actually be the same package) > or otherwise you won't be able to work with both personalities, because if > you install C++ package, then Delphi package won't load (will report that > certain unit is already imported in another loaded package - C++ one) and > visa versa. I'm not sure if I explained the problem, but it seems that > Borland suggests that we have one [pre-build] package for both personalities > and just provide additional lib, obj & hpp files for C++ and dcu dcp for > Delphi. This will not allow users to > open that package and rebuild it, though, because BDS doesn't have > personality-neutral package format and at the same time they must have the > same name... Should we store them in different folders? >> > > You have to use the special command-line dcc32.exe compilation switch /JL to > generate the C++ files from a Delphi package. Other than that, the build > works exactly the same. We keep them separate just because we have always > traditionally kept the two separate (C++ and Delphi). > |
Mon, Jan 29 2007 6:38 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< However, this is not what I asked >> I know, but you kind of answered your own question and I really couldn't add anything else. Borland has set it up so that you can't have two packages referencing the same units loaded at the same time in the IDE. No amount of renaming the packages, etc. is going to solve that issue short of renaming the components and all of the units. There may be a way to load the same package with both personalities, and if so, that would solve it. -- Tim Young Elevate Software www.elevatesoft.com |
Mon, Jan 29 2007 7:51 PM | Permanent Link |
Michael Baytalsky | Tim,
> There may be a way to load the same package with both personalities, and if > so, that would solve it. Yes, that's basically what I was thinking about. Use the same bpl for both personalities and then add separately paths to obj/hpp and dcu files. I just asked because I noticed you didn't do it this way and I sort of wondering maybe there's a reason for that. Thanks, Michael |
Tue, Jan 30 2007 5:40 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Michael,
<< I just asked because I noticed you didn't do it this way and I sort of wondering maybe there's a reason for that. >> Our build system design is such that changing to accomodate both personalities using the same packages isn't quite possible yet without some serious re-arranging. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Saturday, April 27, 2024 at 08:52 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |