Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: secbase error - C++Builder 10.2 Pro Release 1 supports Xcode 8.3 and above?


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 3 - Last Post: Oct 4, 2017 12:33 AM Last Post By: GAI CHEW KAI
GAI CHEW KAI

Posts: 53
Registered: 7/29/04
secbase error - C++Builder 10.2 Pro Release 1 supports Xcode 8.3 and above?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Sep 10, 2017 2:41 AM
Embarcadero® C++Builder 10.2 Version 25.0.26309.314
Android 7.0.1
Microsoft Windows 10 x64 Pro [Version 10.0.14393]
Mac OSX Sierra 10.12.6, Mac Mini ( Late 2012 )

I have installed the C++Builder 10.2 Pro Release 1 which claim to support for latest versions of iOS and Xcode (iOS 10.3 and XCode 8.3.2) when targeting the iOS App Store.

http://edn.embarcadero.com/article/44763

However, with the Xcode 8.3, 8.3.2 both installed both resulted in the following compile error for Mac OSX application:

SecBase.h:

*typedef struct CF_BRIDGED_TYPE(id) SECTYPE(SecCertificate) SecCertificateRef;

I not sure what such error occurs, and now I just switched back to Xcode 8.2.1 that works.

Please advise.

GAI CHEW KAI

Posts: 53
Registered: 7/29/04
Re: secbase error - C++Builder 10.2 Pro Release 1 supports Xcode 8.3 and above?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 2, 2017 9:54 AM   in response to: GAI CHEW KAI in response to: GAI CHEW KAI
...next I do a total clean install by:

- uninstalled the existing Embarcadero® C++Builder 10.2 Version 25.0.26309.314
- delete all Embarcadero\Studio\19.0 directory
- delete all C:\Users\My Name\Documents\Embarcadero\Studio\SDKs
- then re-install with latest 10.2.1 including the the patch for iOS 11.

There is different with direct install of 10.2.1 without uninstalling 10.2 and uninstall 10.2 first then install 10.2.1.
The total cleanup of 10.2 then followed by 10.2.1 install will have the IDE about dialog will show:

Embarcadero® C++Builder 10.2 Version 25.0.27659.1188

Installed Updates:
Delphi 10.2 and C++Builder 10.2 Update 1

However, the result of compiling for MacOSX still the same, SecBase.h error encounter for XCode below:

9
8.3.3
8.3.2
8.3

Until the version that works is 8.2.1

I am not sure why, I have used the XCode 9 via AppStore and separate XCode 9.xip installation, both also failed to compile a simploe MacOSX empty form application.

The MacOSX version is 10.13 detected from SDK Manager.

PAServer at Mac OSX is updated to 10.1.1.37

Please advise.
bernard roussely

Posts: 106
Registered: 2/8/05
Re: secbase error - C++Builder 10.2 Pro Release 1 supports Xcode 8.3 and above?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 3, 2017 11:29 PM   in response to: GAI CHEW KAI in response to: GAI CHEW KAI
Hi,

Have a look at https://forums.embarcadero.com/thread.jspa?threadID=251568&tstart=0

This won't allow you to use the latest Apple SDKs but will allow you to run your app on the latest OSX and iOS versions. The downside is youwon't benefit from the latest fixes and updates.

Regards,

bernard
GAI CHEW KAI

Posts: 53
Registered: 7/29/04
Re: secbase error - C++Builder 10.2 Pro Release 1 supports Xcode 8.3 and above?  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Oct 4, 2017 12:10 AM   in response to: bernard roussely in response to: bernard roussely
Hi Bernard,

> Have a look at https://forums.embarcadero.com/thread.jspa?threadID=251568&tstart=0
- I am aware of such thread, is just the announcement of 10.2.1 is very confusing in the case based on link below:

http://docwiki.embarcadero.com/RADStudio/Tokyo/en/10.2_Tokyo_-_Release_1

...it said "Support for latest versions of iOS and Xcode (iOS 10.3 and XCode 8.3.3) when targeting the iOS App Store."

> This won't allow you to use the latest Apple SDKs but will allow you to run your app on the latest OSX and iOS versions.
- this does not make sense as developer would assumed the latest patch must be able to compile a normal empty OSX form in general apparently :)
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02