Thread View: borland.public.cppbuilder.migration
3 messages
3 total messages
Started by Mark Vejvoda
Wed, 26 Jul 2006 19:25
More warnings about bds 2006 behaviour in C++
Author: Mark Vejvoda
Date: Wed, 26 Jul 2006 19:25
Date: Wed, 26 Jul 2006 19:25
13 lines
1751 bytes
1751 bytes
I created a brand new C++ dll project to have a clean project in bds 2006 and noticed wacky things going on at runtime such as the global Session (bde) variable was not recognizing the databases in it from the calling exe project that loads the dll. After comparing another "clean" dll project that did properly have the session variable set I found that even in my new dll project there were strange settings in the raw project xml file (.bdsproj). Namely removing an entry that had libraries="xxx,xxx,xxx" where xxx where some random packages cause this problem. By removing that and recompiling session was back to normal. FYI.. once you have a good project... back it up for reference! This problem happens bot6h when bds converts and even on new projects when you add in files to it... the project sometimes gets messed up.
Re: More warnings about bds 2006 behaviour in C++
Author: softcoder
Date: Fri, 28 Jul 2006 18:06
Date: Fri, 28 Jul 2006 18:06
40 lines
2800 bytes
2800 bytes
Simple. Create a new C++ dll project, then I added the files that my old bcb6 project had in it. Compiled the dll and ran the project. It seems that sometimes when creating a new dll project the .bdsproj file places entries in the file that cause it to link the final dll so that dynamic rtl is ignored or corrupted. I "think" the main difference I noticed when win-diffing the project files was that the bad project had: name="libraries" value=xxx,xxx" as an entry in it, whereas the good project files do not. Again this is just my guess as I observed what seemed to be different. "David Dean" <ozchzhq02@sneakemail.com> wrote in message news:ozchzhq02-22FD3D.15395227072006@frylock.local... > In article <44c7c1aa@newsgroups.borland.com>, > "Mark Vejvoda" <mark_vejvoda@hotmail.com> wrote: > >> I created a brand new C++ dll project to have a clean project in bds 2006 >> and noticed wacky things going on at runtime such as the global Session >> (bde) variable was not recognizing the databases in it from the calling >> exe >> project that loads the dll. After comparing another "clean" dll project >> that >> did properly have the session variable set I found that even in my new >> dll >> project there were strange settings in the raw project xml file >> (.bdsproj). >> Namely removing an entry that had libraries="xxx,xxx,xxx" where xxx where >> some random packages cause this problem. By removing that and recompiling >> session was back to normal. > > I might still be to half asleep from flying in the red-eye this > morning, but would you mind spelling out the steps you took and the > results you saw in a little more detail? > > -- > -David > > Quis custodiet custodes ipsos?
Re: More warnings about bds 2006 behaviour in C++
Author: softcoder
Date: Fri, 28 Jul 2006 22:23
Date: Fri, 28 Jul 2006 22:23
54 lines
3374 bytes
3374 bytes
Interestingly a collegue of mine who newly installed bds 2006 on his system had the following happen. Opening the project group in bds 2006 the ide automatically inserted the "libraries" entry and added references to idectrls.bpl thus giving errors during the build process on his system, whereas the original code on my system does not have those items in the .bdsproj file in question. "softcoder" <nospam_softcoder@soft-haus.com> wrote in message news:44ca5240$1@newsgroups.borland.com... > Simple. Create a new C++ dll project, then I added the files that my old > bcb6 project had in it. Compiled the dll and ran the project. It seems > that sometimes when creating a new dll project the .bdsproj file places > entries in the file that cause it to link the final dll so that dynamic > rtl is ignored or corrupted. I "think" the main difference I noticed when > win-diffing the project files > was that the bad project had: > > name="libraries" value=xxx,xxx" > > as an entry in it, whereas the good project files do not. Again this is > just my guess as I observed what seemed to be different. > > "David Dean" <ozchzhq02@sneakemail.com> wrote in message > news:ozchzhq02-22FD3D.15395227072006@frylock.local... >> In article <44c7c1aa@newsgroups.borland.com>, >> "Mark Vejvoda" <mark_vejvoda@hotmail.com> wrote: >> >>> I created a brand new C++ dll project to have a clean project in bds >>> 2006 >>> and noticed wacky things going on at runtime such as the global Session >>> (bde) variable was not recognizing the databases in it from the calling >>> exe >>> project that loads the dll. After comparing another "clean" dll project >>> that >>> did properly have the session variable set I found that even in my new >>> dll >>> project there were strange settings in the raw project xml file >>> (.bdsproj). >>> Namely removing an entry that had libraries="xxx,xxx,xxx" where xxx >>> where >>> some random packages cause this problem. By removing that and >>> recompiling >>> session was back to normal. >> >> I might still be to half asleep from flying in the red-eye this >> morning, but would you mind spelling out the steps you took and the >> results you saw in a little more detail? >> >> -- >> -David >> >> Quis custodiet custodes ipsos? > >
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads