-
-
Notifications
You must be signed in to change notification settings - Fork 3
How to get started with development? #2
Comments
I'm finalizing my local work at the moment (usually when I work alone I only write the meta doc when I feel the project is ready) but I'll keep in mind giving at least the minimal details for you guys to begin working on it. |
As of now, both I and @9a24f0 couldn't understand the workflow and models and blah blah of this project. Can you focus on the documentation first, so that we can cooperate more easily? More specifically, something like "Getting started" section of a lib/language. In addition, I believe that some offline discussion could be helpful too. |
I don't believe that belongs to documentation (what in my mind means user reference, which is available online here). Thus I'll explain what to be done here and rename this issue accordingly. So alure is a C++ library, whose functionality is exposed in it's header (alure/include/alure2.h). Our goal is to make that set of functionality (see #5) available on Python using Cython as a bridge. What Cython does is that it translate Cython sauces to a Python extension (a fancy way to call a C/C++ module that can be complied to a Python module). This Python extension can be used in both Python and C/C++ (with A good tutorial for doing this is available at Cython's doc. TLDR:
The main issues are with how to handle cases when it is not that straight forward (not every C++ data type can be automatically converted to Python and vice-versa, so we need to do some extra wrapping, see the beginning of To compile, run
Sure that'd help. The matter is when (take a look at our study schedule lmao). Maybe this friday morning? |
Since you both got started, I'm closing this. |
The current README appears to be incomplete and it's hard for starters to know:
The text was updated successfully, but these errors were encountered: