🚀 go-pugleaf

Craig Farrell wrote:
> Hi,
> >     Building project has no problem. But when we are trying to execute
> > the .exe file. it reports many access violation problems.
> >     Are there anything We should be careful, when we convert the old
> > project into new one?
>
> I suggest creating a brand new project in BDS that is
> similar to the one you are upgrading. Then go to Tools
> | Options | Compiling and Running and turn ON "Show
> command line" and look for obvious differences in the
> switches and libs between the two projects.
> Some ideas:
> -make sure all .obj's and .lib's are being rebuilt by
> deleting them. Don't depend on "Build All"  to do that,
> e.g. you could have #pragma link's in there.
> -Check the switches relating to things like data alignment,
> size of enum's, etc.
> -If you use STL look into that, are you getting the correct
> one?
>
> --Craig

My company also is just getting started on upgrading from BCB 5 Pro to
BDS 2006. Things just aren't working. We're just getting started, but
even our simplest apps aren't yet running. I can get one app that links
to a very small set of DLLs to load, but to do it the exe has to delay
load the dll, and that dll has to delay load all of it's DLLs. Further,
I've been having to cannibalize functionality until it loads. I didn't
have to do this in BCB 5. And delay loading DLLs does not help any
other apps.

Since it's the weekend, I'm not next to the machine that has the new
builder on it, so I can't look myself. Your statement about getting the
correct STL is interesting to me. We use the STL in almost every file.
Which options do I have for the STL? I thought Dinkumware was the only
option out of the box. What are the advantages to each? How do I pick
it? (yeah, I should probably wait until Monday and look myself... but
you piqued my interest with that one).

With respect to our DLLs, I can set breakpoints in each entry point,
and I don't get there. Not until I make a very small app, that delay
loads a small set of them, and then slowly remove code from many of the
DLLs. I'm at a loss at this point as to what's wrong... especially
since this worked in BCB 5. I did wind up regenerating most of my
projects because the converter flat out screwed it up.

This has been far from a painless upgrade. And the complete lack of
usability of the borland command line tools is utterly frustrating. We
wound up making our own project parser that goes and fixes the
generated makefiles (yes, I've seen the other ones out there, but they
don't quite fit our environment, and we can't use pre-compiled headers
like one of them tries to get you to do).

... and I'll stop now before I start ranting.