Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error: no member named 'int16' in namespace 'ceres' #1

Open
ubuntuslave opened this issue May 6, 2015 · 6 comments
Open

error: no member named 'int16' in namespace 'ceres' #1

ubuntuslave opened this issue May 6, 2015 · 6 comments

Comments

@ubuntuslave
Copy link

I'm trying to build cyres by going to the source folder and running:

python setup.py build

but I get errors relating to the ceres::int16 data type not existing. Is this a Cython issue with clang on Mac OS X?

@arjun810
Copy link
Member

arjun810 commented May 7, 2015

What version of ceres-solver are you trying to build with? My hunch is it's related to not having updated cyres to work with the most recent version.

@ubuntuslave
Copy link
Author

I home-brewed ceres-solver version 1.10.0. In addition, I'm using Numpy 1.9.2 and cython 0.22. Do you recall which version of ceres-solver worked for you?

@arjun810
Copy link
Member

arjun810 commented May 7, 2015

I've got 1.8.0 right now. I think it changed in a recent version of ceres, and it looks like someone actually fixed this in a fork:
PolarNick239@1fb4674

I generally go through and make similar fixes every time I upgrade ceres, but I haven't upgraded recently.

@ubuntuslave
Copy link
Author

I fixed this problem by changing the data type from int16 to int32 in a couple of files in the src folder.

In addition. I had to avoid linking to GPU-related libraries that my system doesn't support (for exemple, "cholmod", "camd", "amd", "colamd", "cxsparse") in the setup.py script.

I'm not sure if I should create pull request since this only solves my particular problem. I think a more dynamic setup.py is needed.

@lpsinger
Copy link

I wonder if @PolarNick239 could make a pull request for 1fb4674? That commit fixed this issue for me.

@PolarNick239
Copy link

I am sorry, I forgot/not realized to do so. Will do soon (in a couple of days).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants