Building with another SDK in Carbide
I'm trying to switch from codewarrior to carbide.
Right now in CW, I have a project that I'm compiling with S60 SDK 2nd edition FP3. But then, I want to compile it for S60 SDK V3. So I just close the project and reimport the MMP file and specify the SDK I want to use.
In carbide, I also have a project. Initially I specified only the S60 SDK 2nd edition FP3 in the build configuration. Then for some reason (e.g. I just installed a new SDK, and of course, that SDK is supported in Carbide), I want to compile it with another SDK (e.g. S60 SDK V3). How am I supposed to do that when that SDK doesn't appear in the "build configuration" view? Is there a way for reimporting the project and specify the SDK I want to use?
Of course, I don't have a MMP, because Carbide doesn't seem to generate one, so I can't use the option "Symbian MMP file" for reimporting
Re: Building with another SDK in Carbide
In the current Carbide.c++ version you basically only get one shot at setting the target SDKs, either when you create or import a project (this will change in the future).
However, there are things that you can do but these are not supported, so I would advise to use caution.
If you later notice that you need a different SDK, you can "re"import the project in the following way (but make a backup copy of your project!)
- Delete the project (but make sure you have the "Do not delete contents" option selected)
- Do a new import of the project and select those SDKs that you need, the project will become "reincarnated" and should have all code changes that you have done (even if your .mpp is only partially correct, like the original .mmp that you used when you first imported). If you have created your project from a template you need to create some kind of .mmp file.
Note however that the build setups for S60 2nd Ed and 3rd Ed are so different that you should really only choose one or the other for a project. The templates enforce this rule but importing you can select both 2nd ed and 3rd ed SDKs. However the set of files as well as file content for 2nd Ed and 3rd Ed are so different that it is difficult to maintain a project for both 2nd and 3rd.