stsievert/swix

Detailed steps for installing swix on a new project

Closed this issue · 12 comments

Please give a detailed and working steps for installing swix on a new project.
I tried several times to follow the given steps.
First I found that OpenCV must be added as Framework in order to compile the project.
In this way the project compiles but the functions cannot be called in any swift file, how to make swix to work?

Many thanks

I do include some instructions on Installation. Theres no section on integrating with an existing project but I believe following step 4 under creating a new project that uses swix can link to the proper frameworks/etc.

I believe this is related to issue #23, reformatting for use with the Swift package manager -- I believe these compiler-linking parameters are specified in some text file. I'm not currently actively developing this (I'll probably fix #23 over the summer), so please feel free to ask further questions/post screenshots/etc. I'll do my best to answer.

Maybe I wasn't clear your instructions does not work.
The tutorial that you give is perfect I can tests everything in it. But I cannot create a new project because the library commands do not work.
I followed ALL the steps and the project does not compile.
You might miss some steps in your instructions. Such as adding OpenCV framework (only one I figured out) and maybe something else.
Adding OpenCV framework I can compile but I cannot call your functions

swix

why my swix folder has a different color respect to the tutorial? Something is missing?

Hm, this sounds like the swix files aren't included in the project -- Xcode doesn't know where to look to find these functions. I'm pretty sure this issue is caused by the process of adding source files to an Xcode project. I normally follow this process: http://stackoverflow.com/a/15195403

It was all Xcode's fault! I made a cache cleaning of the system and Xcode folders.
I manage to include your stuff in my custom project! Thanks for the support!!

I'll add a tip to the installation guide to clean the cache. Thanks for testing and using!

To be clear, you selected Product > Clean? That fixed your issue?

Nope. I deleted the 'Derived Data' folder of Xcode in the Library of my user.
Moreover I'd add the following pic to your instructions while you say to include the folder 'swix'.
unnamed

Many thanks again for your support and your amazing work.
Please keep it up I'd like to see how is it going to develop.
Just to ask a thing, any change to have multi-dimensional arrays in the near future?

Thanks, I'll revise the swix docs with that picture.

Only 1D and 2D arrays (aka vectors and matrices) are currently supported. This is all I saw the need to develop. The code for 1/2D arrays is pretty stable and I don't plan on changing it anytime soon.

On Mar 19, 2016, 5:56 PM -0600, sniis84notifications@github.com, wrote:

Nope. I deleted the 'Derived Data' folder of Xcode in the Library of my user.
Moreover I'd add the following pic to your instructions while you say to include the folder 'swix'.

Many thanks again for your support and your amazing work.
Please keep it up I'd like to see how is it going to develop.
Just to ask a thing, any change to have multi-dimensional arrays in the near future?


You are receiving this because you modified the open/close state.
Reply to this email directly orview it on GitHub(#24 (comment))

So if you had added swix while checking the "copy items if needed" the issue would have been avoided?

You must have "copy items if needed and "create groups".
In my case, if I don't do this at the first time I had to clean the "DerivedData" Xcode folder in my Library.
That is the main important step for the installation.

Thanks for the clarification.

On Mar 20, 2016, 2:09 AM -0600, sniis84notifications@github.com, wrote:

You must have "copy items if needed and "create groups".
In my case, if I don't do this at the first time I had to clean the "DerivedData" Xcode folder in my Library.
That is the main important step for the installation.


You are receiving this because you modified the open/close state.
Reply to this email directly orview it on GitHub(#24 (comment))