obs.icns now corresponds to Table 5-1:
icon_512x512@2x	-	1024 x 1024
icon_512x512	-	512 x 512
icon_256x256@2x	-	512 x 512
icon_256x256	-	256 x 256
icon_128x128@2x	-	256 x 256
icon_128x128	-	128 x 128
icon_32x32@2x	-	64 x 64
icon_32x32	-	32 x 32
icon_16x16@2x	-	32 x 32
icon_16x16	-	16 x 16
Include $ORIGIN in portable mode on unix
Fixup OSX Rpath for imported external libraries on install
Change library search order to match include search order
Merge pull request #34 from BtbN/master

Include $ORIGIN in portable mode on unix
Add explicit Cocoa dependency for osx desktop capture test

Fixes build due to missing objective c functions on some configurations
Rename osx desktop capture functions to fix dynamic loading
Merge pull request #33 from andy-kliman/master

I rebuilt obs.icns. Now it corresponds to Table 5-1:
Add a couple more setting data safety measures

Prevent null dereferencing if data is null, instead just make the
functions return and ignore the get/set requests.
Improve safety for settings usage

- Add 'set_default' functions to obs-data.*.  These functions ensure
  that a paramter exists and that the parameter is of a specific type.
  If not, it will create or overwrite the value with the default setting
  instead.

  These functions are meant to be explicitly called before using any of
  the 'get' functions.  The reason why it was designed this way is to
  encourage defaults to be set in a single place/function.

  For example, ideal usage is to create one function for your data,
  "set_my_defaults(obs_data_t data)", set all the default values within
  that function, and then call that function on create/update, that way
  all defaults are centralized to a single place.

- Ensure that data passed to sources/encoders/outputs/etc is always
  valid, and not a null value.

- While I'm remembering, fix a few defaults of the main program config
  file data.
Improve setting type consistency
Improve multi instance support for osx desktop capture

Fixes behavior with multiple desktop captures in the same scene

Also create the dispatch_queue without a name to prevent name collisions
Use recursive mutex for scene mutex

Fixes a deadlock when trying to remove a source from the GUI. The scene
item signal handlers would mark the source as removed which results in
the video thread also trying to run obs_sceneitem_destroy thereby
deadlocking the video thread (and the GUI thread)
Check if scene item is actually alive when calling obs_sceneitem_destroy

Prevents a double free in case the scene item was previously removed
Lock graphics before trying to remove a scene item

Prevents another deadlock if removing the scene item triggers source
cleanup of a source with graphics resources
Fix obs_sceneitem_destroy for scenes with more than one scene item
Fix the design flaw with obs_sceneitem_destroy

The previous commit used the scene as a  parameter to check to see if
the scene item was still present within the scene before destroying, but
this was actually unnecessary because the fault was because the destroy
signal was being triggered *before* the scene's mutex locked, thus
causing a race condition.  I changed the code so that it signals after
the lock instead of before, so the scene parameter should no longer be
necessary.
Merge branch 'master' of https://github.com/jp9000/obs-studio
Improve thread safety for scene items

Scene items previously were removed by calling obs_sceneitem_destroy,
but this proved to be a potential race condition where two different
threads could try to destroy the same scene item at the same time.

Instead of doing that, reference counting is now used on scene items,
and an explicit obs_sceneitem_remove function is used instead for item
removal, which sets a 'removed' variable to ensure it can only be called
exactly one time.
Use mutex instead of variable for RC check