OS X -framework and -F flags not handled

[GoogleCodeExporter]

What steps will reproduce the problem?

1. ctypesgen [options] -framework SomeFramework

What is the expected output? What do you see instead?

ctypesgen.py: error: no such option: -f

What version of the product are you using? On what operating system?

SVN r125, OS X 10.x.

Please provide any additional information below.

OS X frameworks are another type of shared library, so they should be handled 
similar to libraries (dyld should handle them just like .dylib libraries).

Locating them is different.  -F/path/to/folder is used like -L to add to the 
search path (another option ctypesgen needs to handle).  DYLD_FRAMEWORK_PATH is 
the equivalent env var to DYLD_LIBRARY_PATH.  File names are in the form 
/path/to/framework/folder/SomeFramework.framework/SomeFramework, which is 
usually an alias to a specific version 
.../SomeFramework.framework/Versions/[version]/SomeFramework, no file extension.

Original issue reported on code.google.com by kyngch...@kyngchaos.com on 28 Jan 2011 at 5:28

[GoogleCodeExporter]

This sounds like an enhancement request rather than a defect.

It looks like this needs a Mac developer as this request appears to be OS X 
specific.

Original comment by clac...@gmail.com on 28 Jan 2011 at 5:43

[GoogleCodeExporter]

I'd call it a defect - it's essentially broken, but nobody has run into it 
until now (or have worked around it and not said anything).

Anyways, if there are no active Mac developers for ctypesgen, and if I can 
figure out how ctypesgen works (I have a general idea), I can look into it.

Mainly I'm not sure how to add the separated -framework option, ie flag + space 
+ value, all the others I might use as an example have no space.  Maybe it's 
automatic in the option parser?

Original comment by kyngch...@kyngchaos.com on 28 Jan 2011 at 6:02

[GoogleCodeExporter]

Assigning to myself.

Original comment by jcscoob...@gmail.com on 28 Jan 2011 at 6:44