Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Installation paths did wrong, propose new one, more accurate like SDK DONE it #12

Open
genose opened this issue Nov 11, 2016 · 1 comment

Comments

@genose
Copy link

genose commented Nov 11, 2016

Hi, i'm tracking path in Install CDT and many strange path construction and thinks appear

  • 1 . Why we got a 'pwd'..'i386-pc-mingw32msvc"
    1. WTF
      so take a look on your Mac (if you have one , Linux Support in progress )
      just do :
      ls -la /Applications/Xcode.app/Contents/Developer/Platforms/
      So you got
      iphone.platform
      MacOS.platform
      contains -- > > : Developer Entitlements.plist Info.plist OS X.icns ResourceRules.plist usr version.plist
      in MacOS.platform/Developer
      contains -- > > : SDKs/MacOSX10.4u.sdk/ ( i use 10.4 and 10.6 for my Projects )
      contains -- > > : Developer Library SDKSettings.plist System usr

Cocotron's path is quite messy :
/Developer/Cocotron/1.0/
Downloads PlatformInterfaces Source Windows bin build

and some file in Install CDT ... why ??

So, i work on this to provide a more elegant path, cause of Template on Xcode i work on Too 👍
SDK_ROOT=Developer/Platforms/{Targetted_System}.platform/Developer/SDKs/{System_Version}/
{SDK_ROOT}/tmp/Download
{SDK_ROOT}/tmp/build
{SDK_ROOT}/tmp/Source
{SDK_ROOT}/PlatformInterfaces
and i tested it
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk/
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//System/Library/CoreServices
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//System/Library/Frameworks < < -- all the framework should be build HERE
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//System/Library/Printers
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//System/Library/PrivateFrameworks
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//usr
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//usr/bin
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//usr/include
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//usr/lib
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//usr/libexec
/Applications/Xcode.app/Contents/Developer/Platforms/windows.platform/Developer/SDKs/windows7.sdk//usr/share

What did you think about this change ?

@genose genose changed the title Installation paths Installation paths did wrong, propose new one, more accurate like SDK DONE it Nov 11, 2016
@cjwl
Copy link
Owner

cjwl commented Nov 28, 2016

"i386-pc-mingw32msvc" is a gcc target triplet, this specifies a process/os-runtime combination. You need to differentiate between processors and OS/runtime combinations. For example "windows7" means nothing, you need to differentiate 32-bit vs. 64-bit and the targeted runtime, cygwin vs. mingw (vs something else).

I would discourage the use of .platform or .SDK as these are basically Xcode private organizations and not needed to make things work.

There have been a number of recent changes which place a lot of libraries/headers relative to a working copy which is what you really need for headers/libraries because absolute locations are no good as you can't easily test multiple installs. Installing the compiler in a relative location would be handy too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants