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

Is it available to run ODM on Windows #247

Closed
xialang2012 opened this issue Feb 18, 2016 · 13 comments
Closed

Is it available to run ODM on Windows #247

xialang2012 opened this issue Feb 18, 2016 · 13 comments

Comments

@xialang2012
Copy link

Just curious... I have checked the libraries which used by ODM, it seems most of the libraries have the Windows version, except the gsl.

@dakotabenjamin
Copy link
Member

I've never tried to build it on windows, as is I don't think it will work. But if what you say is true, maybe it could be installed manually with gsl for windows

@xialang2012
Copy link
Author

Okay, If I have enough time, I will try it.

@xialang2012
Copy link
Author

I have already successful built ODM on Windows with VS 2013.

@dakotabenjamin
Copy link
Member

I will have to try this! What did you do to make it work?

@smathermather
Copy link
Contributor

Whoa! Awesome.

@xialang2012
Copy link
Author

@dakotabenjamin The compatibility of the ODM is very well, I have never revised any codes on it. Just built Opencv 3.0, PCL 1.7.2 (it is wise to use all in to installer), PROJ 4.8 on Windows with VS 2013, then built the modules of the ODM respectively. The include and library paths, the libraries used are as below:

C:\Program Files\PCL 1.7.2\include\pcl-1.7;C:\Program Files\PCL 1.7.2\3rdParty\Eigen\eigen3;C:\Program Files\PCL 1.7.2\3rdParty\Boost\include\boost-1_55;C:\Program Files\PCL 1.7.2\3rdParty\FLANN\include;C:\Program Files\PCL 1.7.2\3rdParty\QHull\include;C:\Program Files\PCL 1.7.2\3rdParty\VTK\include\vtk-5.10;D:\opencv3\build\include;E:\gdal\proj-4.8.0\src;

C:\Program Files\PCL 1.7.2\lib;C:\Program Files\PCL 1.7.2\3rdParty\Boost\lib;C:\Program Files\PCL 1.7.2\3rdParty\VTK\lib\vtk-5.10;E:\opencv3\lib\Release;E:\gdal\proj-4.8.0\src;

pcl_common_release.lib;pcl_io_release.lib;pcl_surface_release.lib;pcl_kdtree_release.lib;vtkCommon.lib;opencv_core300.lib;opencv_imgproc300.lib;opencv_imgcodecs300.lib;opencv_highgui300.lib;proj_i.lib;

@ahmadusman
Copy link

xialang can you share work, I have tried but its getting error

@GeospatialDaryl
Copy link
Contributor

Hi-

I've put a fair amount of effort into making the ODM structure platform
independent.

Other than OpenSfM, most of the components compile pretty readily on VS2013

  • with some tweaking. Thinking long-term, there are some basic conventions
    in python programming that can ensure cross-comparabilit (e.g. use os.sep,
    etc).

Daryl

On Fri, Mar 4, 2016 at 7:59 AM, ahmadusman notifications@github.com wrote:

xialang can you share work, I have tried but its getting error


Reply to this email directly or view it on GitHub
#247 (comment)
.


Daryl Van Dyke
GIS Analyst
Klamath Strategic Habitat Conservation Team
US Fish & Wildlife Service - AFWO, R8
(707) 825-5153
https://github.com/GeospatialDaryl

@dakotabenjamin
Copy link
Member

@ahmadusman can you post your errors? I'd like to get around to this at some point in the near future.

@ahmadusman
Copy link

I have manually installed all the dependencies but its still asking for more every time I build it

@ahmadusman
Copy link

Missing Dependencies

@xialang2012
Copy link
Author

@GeospatialDaryl, yes, the problem is the openSFM, but we can used visualSFM or openMVG to replace it. (visualSFM is not an open-source project...)

@dakotabenjamin
Copy link
Member

Given the modular nature of the project, if in the future we want to get Windows support fully and OpenSfM isn't supported by then, we could probably sidle openMVG in as a replacement for windows builds. I think OpenSfM is the best option in general so it shouldn't be replaced.

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

No branches or pull requests

5 participants