Structural questions

M

Manfred Aabye

Member
I have a couple of strange questions about the viewer ;)
1. What are all the Python scripts for?
Are all just to build the viewer with autobuild or is the viewer based partly on Python?
2. Visual Studio asked me which is the startup file?

Ich habe da ein Paar merkwürdige fragen zum Viewer ;)
1. Wofür sind eigentlich die ganzen Python Skripte?
Sind die alle nur zum bauen des Viewers mit autobuild oder basiert der Viewer zum teil auf Python?
2. Visual Studio fragte mich welches denn die Startdatei sei?
 
It depends on which version viewer you use. The SL viewer have the SL Viewer Manager coded in Python. It is used to launch the viewer, check for and install updates.

The Dayturn viewer should not have any python scripts at all installed.

Autobuild and a number of utility scripts for building, packaging and testing the viewer exist in the source repository, and the viewer cannot per date be built without them unless you significantly restructure the dependency resolution and build process.
 
Why don't you actually try and build the viewer, and you would find out that it is actually cmake that generates the projects that builds the viewer with VS or Xcode. ;)
 
Yes, I have already looked at many cmake.txt files.
But it must seem to get something from autobuild.

Ja ich habe mir schon viele cmake.txt Dateien angesehen.
Es muss aber anscheinend etwas von autobuild bekommen.
 
Autobuild is primarily a dependency manager that generates, feeds information to and invokes cmake when building the viewer from the command line.
The autobuild configure process generates VS or Xcode projects with all the dependencies from the external libraries resolved that can be built inside the two IDEs, but even then cmake is involved.

If you open the project in VS, it will analyse well over 140000 #include references in the solution.
 
14000 that's probably because it's all there three times, so Win, Mac and Linux.
Most references are apparently directory paths as well as copying files, as I can see.
Is there a tutorial on how to create the viewer without autobuild, maybe an old tutorial where there was no autobuild yet?

14000 das ist wahrscheinlich weil dort alles dreimal eingetragen ist, also Win, Mac und Linux.
Die meisten Referenzen sind anscheinend Verzeichnis pfade sowie das kopieren von Dateien, so wie ich das sehen kann.
Gibt es eine Anleitung wie man den Viewer ohne autobuild erstellt, vielleicht eine alte Anleitung, wo es noch kein autobuild gab?
 
As I told you before, you cannot build the viewers without autobuild without taking on a massive restructuring of the project.

Cool VL viewer will most likely build without autobuild. The source is here sources. The build instructions are minimal.

You are also wrong about installing all three times. Autobuild will only install libraries for the architecture you build on. You cannot build the macOS version on anything else than macOS, the Windows version on anything else than Windows or Linux version on a machine running some Linux distro.

I build the macOS version native on macOS, and the Windows version in a vmware virtual machine running Windows 7.
 
Manfred Aabye said:
CoolVLViewer-src-1262262 works (VS2013)
CoolVLViewer-src-1262315 works (VS2017)
Click to expand...
OK

It is not so interesting for this viewer at this stage as Henri have structured his viewer very different from those built on LL version2.

The macOS version is most likely to be completely restructured as a proper Xcode project not using cmake at all.
 
You must log in or register to reply here.

Members online

No members online now.
Total: 5 (members: 0, guests: 5)
Back
Top