AppVeyor: Update build environment and save artifacts

[EwoutH]

• Updates the build environment to the Visual Studio 2019 image
• Use Python 3.8 in AppVeyor builds
• Saves the build folder as an artifact

[EwoutH]

Blocked by #874.

[natowi]

• rename build to meshroomWin64snapshot%APPVEYOR_PULL_REQUEST_HEAD_COMMIT%.zip
  so we can better distinguish the builds.

[EwoutH]

Thanks for the quick reply. It's not that quick, since build refers to the build folders path. I implemented it with an dedicated zip command though. Example here.

What do you think of #874?

[EwoutH]

Can someone give me a hand how to build a standalone / release version of Meshroom? (so including aliceVision and the qtPlugins)

[fabiencastan]

Hi @EwoutH,

Thanks for the PRs.
I'm not sure what is the best way to create standalone binaires.
You can have a look at the dockerfiles:

• https://github.com/alicevision/meshroom/blob/develop/Dockerfile_deps
• https://github.com/alicevision/meshroom/blob/develop/Dockerfile

The docker files are relying on the dockerhub images of AliceVision.
The problem is that it needs binaries of AliceVision aligned with the current branch....

[natowi]

It is possible to load builds from other Appveyor sessions. I looked into this when I was updating the AliceVision Appveyor file.
https://help.appveyor.com/discussions/questions/19858-accessing-build-artifacts-from-one-project-in-another
I think it should be possible to merge existing builds of the components or write an Appveyor script to copy all dependencies into the environment and put together a complete build.

But I think before we look into this, we should also save build artifacts for https://github.com/alicevision/QtOIIO and https://github.com/alicevision/qmlAlembic

[EwoutH]

The PRs referenced above enable saving build artifacts for QtOIIO and qmlAlembic. From both projects, the whole build folder is saved as .zip, and the following artifacts are also save separately:

• alembicEntityQmlPlugin.dll
• alembicEntityQmlPlugin.lib
• QtOIIOPlugin.dll
• QtOIIOPlugin.lib
• depthMapEntityQmlPlugin.dll
• depthMapEntityQmlPlugin.lib

Is anything else needed from those two projects?

[natowi]

@EwoutH Oh, yes, I missed to mention https://github.com/alicevision/QtAliceVision
We could use an appveyor build for that, too.

https://github.com/alicevision/meshroom/blob/665f0b8c28d48ee27091b44f8e7be79f0b62aec3/meshroom/__init__.py#L47

Meshroom standalone structure

• Meshroom/

  • Meshroom # main executable

  • COPYING.md # Meshroom COPYING file

  • aliceVision/

    • bin/ # runtime bundled binaries (windows: exe + libs, unix: executables)
    • lib/ # runtime bundled libraries (unix: libs)
    • share/ # resource files
      • aliceVision/
        • COPYING.md # AliceVision COPYING file
        • cameraSensors.db # sensor database
        • vlfeat_K80L3.tree # voctree file

• lib/ # Python lib folder

• qtPlugins/

  • imageformats
    • QtOIIOPlugin dll/lib
  • qml
    • AlembicEntity
      • alembicEntityQmlPlugin dll/lib
    • AliceVision
      • qtAliceVisionPlugin dll/lib
    • DepthMapEntity
      • depthMapEntityQmlPlugin dll/lib

[EwoutH]

I would suggest merging this now. I will open an separate PR for release builds, probably using GitHub Actions.

[jure]

This appears to be a very minimal and non-invasive PR that greatly simplifies testing the latest dev builds. 👍

[jure]

The added comment invalidated the review although no code changes occurred. The original review by @simogasp is probably equally applicable to this latest code.

[jure]

Yay, works! 🎉 E.g. https://ci.appveyor.com/project/AliceVision/meshroom/builds/34184086/artifacts