mattneub / appscript Goto Github PK

objc-appscript comes with 6 separate build configurations, each of which hardcodes either 10.4u or 10.5 SDK. Plus, the 10.4 ones require gcc 4.0, and both specify ppc architectures.

This means you can't build with recent versions of Xcode; as of 4.5, the oldest SDK you can use is 10.7, there's no gcc 4.0, and no ppc or ppc64 compiler.

Fixing this locally isn't too hard if you know what you're doing. Here's how to do it in the Xcode 4 GUI:

• In the project Info, delete the 10.4 configs, and rename the 10.5 configs to remove the "10.5" from the names.
• Switch to build settings, change Architectures for just the two Release configs to Standard (or whatever ${ARCHS_STANDARD_32_64_BIT} is called in your version of Xcode's GUI).
• Set the Base SDK for all three configs to Latest OS X.
• Set the OS X Deployment Target for all three configs to OS X 10.5.

This works at least back to Xcode 3.1.1 on a 10.5 i386 machine.

But of course it removes the ability to do 10.4 builds, and PPC builds, and it could break build scripts that people have written to wrap Appscript xcodebuild.

So, it might be better to leave the 10.4 and 10.5 configs alone, create 3 new "Latest" configs that are cloned from the 10.5 configs, then apply the changes above to the new configs only.

Some files are installed differently with the rb-appscript gem when using ruby 2.0. This may be a problem with the gemspec. The effect is that nothing can be loaded.

For example, the lib/_aem is a directory when installed with ruby 1.9.3, but is a file in 2.0:

$ ls /Users/tee/.rvm/gems/ruby-1.9.3-p374/gems/rb-appscript-0.6.1/lib/_aem/
aemreference.rb     connect.rb      findapp.rb      send.rb
codecs.rb       encodingsupport.rb  mactypes.rb     typewrappers.rb

$ ls /Users/tee/.rvm/gems/ruby-2.0.0-p0/gems/rb-appscript-0.6.1/lib/_aem/
ls: /Users/tee/.rvm/gems/ruby-2.0.0-p0/gems/rb-appscript-0.6.1/lib/_aem/: Not a directory

$ cat /Users/tee/.rvm/gems/ruby-2.0.0-p0/gems/rb-appscript-0.6.1/lib/_aem 
#
# rb-appscript
#
# typewrappers -- Ruby classes representing type, enumerator, property and keyword AEDescs
#

module TypeWrappers

    class AETypeBase

        attr_reader :code
...     

Hi, thanks for keeping this alive.

I have a legacy project that depends on project sprouts, which depends on rb-appscript.

Whether I install it as a gem, or make manually, I get the same errors:
gem_make_out.txt

Has anyone had success with rb-appscript in 10.12? The last version I installed it under was 10.8.

Thanks,

Stray

When trying to install another gem (consular-iterm), it fails while trying to install rb-appscript with the following error:

ERROR:  Error installing consular-iterm:
  ERROR: Failed to build gem native extension.

    /Users/erichu/.rvm/rubies/ruby-2.2-head/bin/ruby -r ./siteconf20150729-1786-1m2j7h9.rb extconf.rb
*** extconf.rb failed ***
Could not create Makefile due to some reason, probably lack of necessary
libraries and/or headers.  Check the mkmf.log file for more details.  You may
need configuration options.

Provided configuration options:
  --with-opt-dir
  --with-opt-include
  --without-opt-include=${opt-dir}/include
  --with-opt-lib
  --without-opt-lib=${opt-dir}/lib
  --with-make-prog
  --without-make-prog
  --srcdir=.
  --curdir
  --ruby=/Users/erichu/.rvm/rubies/ruby-2.2-head/bin/$(RUBY_BASE_NAME)
extconf.rb:44:in `<main>': uninitialized constant Config (NameError)

extconf failed, exit code 1

There was a similar error reported for another gem and the cause is that
Ruby 2.2 changes the Config global namespace to RbConfig.

In the Python scripts for this project, I find extra_path = "aeosa", which according to Python #27919 is deprecated.

If this feature is something on which you rely heavily, please feel free to post back to the Python ticket explaining your use case and why you think this feature should be retained.

Thanks.