ADS eval compiler prob w/BREW v2.0 SDK | developer.brewmp.com ADS eval compiler prob w/BREW v2.0 SDK | developer.brewmp.com

Developer

ADS eval compiler prob w/BREW v2.0 SDK

I've received indications from multiple sources that the ADS v1.2 evaluation compiler will generate executables that crash on the handset when compiled with BREW v2.0 SDK.

RVCT v1.2 will not do this. I do not know if the fully licensed version of ADS v1.2 does this.

If you are run into this problem, you can use the BREW v2.1 SDK even on a v2.0 phone, if you use only v2.0 and previous APIs.

Also, it appears that the ADS v2.0 evaluation compiler is a limited version. I'm not exactly sure what those limitations are, but it appears that it will not compile large source files.
--t

How 'bout the 1.1 SDK? Everything I've compiled thus far has just crashed and given me a black screen. No errors or warnings, at least not that I've noticed (and its been a couple hours since I last tried).
Also I'm using ADS 1.2 (trial)... is there any difference between ADS and RVCT in terms of the compiler? Or is just the packaging that comes with the compiler thats different?
Oh, and in case anyone is wondering, the resulting MOD, while it doesn't work, is 22% smaller than the GCC compiler version. Now if I can just get it to run... :D

How 'bout the 1.1 SDK? Everything I've compiled thus far has just crashed and given me a black screen. No errors or warnings, at least not that I've noticed (and its been a couple hours since I last tried).
Also I'm using ADS 1.2 (trial)... is there any difference between ADS and RVCT in terms of the compiler? Or is just the packaging that comes with the compiler thats different?
Oh, and in case anyone is wondering, the resulting MOD, while it doesn't work, is 22% smaller than the GCC compiler version. Now if I can just get it to run... :D

It works fine with BREW 1.1.
There are a number of reasons why it would crash the handset without a warning. You might try building a tiny test app first...

It works fine with BREW 1.1.
There are a number of reasons why it would crash the handset without a warning. You might try building a tiny test app first...

Are you using makefiles that came with the 1.1 SDK? I believe it mentions in the makefile that it's only compatible with 1.0 ADS. Try using the makefiles from a different version of the SDK, or generating your own with the Visual Studio addins.

Are you using makefiles that came with the 1.1 SDK? I believe it mentions in the makefile that it's only compatible with 1.0 ADS. Try using the makefiles from a different version of the SDK, or generating your own with the Visual Studio addins.

Just how important is it to have that -g compiler debug flag in the makefile, anyway? Is it essential for BREW apps to run, or does it just get overrun anyway by the optimization commands -Ospace -O2?
All the sample makefiles seem to do it...

Just how important is it to have that -g compiler debug flag in the makefile, anyway? Is it essential for BREW apps to run, or does it just get overrun anyway by the optimization commands -Ospace -O2?
All the sample makefiles seem to do it...

You were absolutely right about the makefiles. Using the SDK 2.1 makefiles fixed it up right away. It was just my luck that I was downloading SDK 2.1 when Qualcomm went down for routine maintainance last night... drove me batty for two hours waiting! Who does maintainance at 8:00 on a Wednesday, anyway?
But its fixed now. As for -g, I think that just puts debug information in the .elf, and the fromelf tool strips it out when it makes the MOD. So, if I'm not mistaken, its not only unnecessary, but its pretty much useless, because nothing (to my knowledge) runs BREW ELFs.

You were absolutely right about the makefiles. Using the SDK 2.1 makefiles fixed it up right away. It was just my luck that I was downloading SDK 2.1 when Qualcomm went down for routine maintainance last night... drove me batty for two hours waiting! Who does maintainance at 8:00 on a Wednesday, anyway?
But its fixed now. As for -g, I think that just puts debug information in the .elf, and the fromelf tool strips it out when it makes the MOD. So, if I'm not mistaken, its not only unnecessary, but its pretty much useless, because nothing (to my knowledge) runs BREW ELFs.