Home › Forums › AR Sandbox Forum › stopped at an error
- This topic has 5 replies, 3 voices, and was last updated 1 year, 10 months ago by marcocspc.
-
AuthorPosts
-
January 3, 2023 at 8:21 am #2419romulogeoflowParticipant
n file included from Vrui/Vislets/FrameRateViewer.cpp:24:
/home/nadedrm/src/Vrui-8.0-002/Vrui/Vislets/FrameRateViewer.h:41:9: error: ‘size_t’ does not name a type
41 | size_t historySize; // Default size of history buffer
| ^~~~~~
/home/nadedrm/src/Vrui-8.0-002/Vrui/Vislets/FrameRateViewer.h:29:1: note: ‘size_t’ is defined in header ‘<cstddef>’; did you forget to ‘#include <cstddef>’?
28 | #include <Vrui/Vislet.h>
+++ |+#include <cstddef>
29 |
/home/nadedrm/src/Vrui-8.0-002/Vrui/Vislets/FrameRateViewer.h:60:9: error: ‘size_t’ does not name a type
60 | size_t historySize; // Number of frame rate measurements in the history buffer
| ^~~~~~
/home/nadedrm/src/Vrui-8.0-002/Vrui/Vislets/FrameRateViewer.h:60:9: note: ‘size_t’ is defined in header ‘<cstddef>’; did you forget to ‘#include <cstddef>’?
Compiling Vrui/Vislets/HMDCameraViewer.cpp…
Compiling Vrui/Vislets/IKAvatarRenderer.cpp…
Vrui/Vislets/FrameRateViewer.cpp: In constructor ‘Vrui::Vislets::FrameRateViewerFactory::FrameRateViewerFactory(Vrui::VisletManager&)’:
Vrui/Vislets/FrameRateViewer.cpp:52:10: error: class ‘Vrui::Vislets::FrameRateViewerFactory’ does not have any field named ‘historySize’
52 | historySize(1024)
| ^~~~~~~~~~~
Vrui/Vislets/FrameRateViewer.cpp:64:9: error: ‘historySize’ was not declared in this scope
64 | historySize=cfs.retrieveValue<unsigned int>(“./historySize”,(unsigned int)(historySize));
| ^~~~~~~~~~~
Vrui/Vislets/FrameRateViewer.cpp: In constructor ‘Vrui::Vislets::FrameRateViewer::FrameRateViewer(int, const char* const)’:
Vrui/Vislets/FrameRateViewer.cpp:122:10: error: class ‘Vrui::Vislets::FrameRateViewer’ does not have any field named ‘historySize’
122 | :historySize(factory->historySize),
| ^~~~~~~~~~~
Vrui/Vislets/FrameRateViewer.cpp:122:31: error: ‘class Vrui::Vislets::FrameRateViewerFactory’ has no member named ‘historySize’
122 | :historySize(factory->historySize),
| ^~~~~~~~~~~
Vrui/Vislets/FrameRateViewer.cpp:136:41: error: ‘historySize’ was not declared in this scope; did you mean ‘history’?
136 | historySize=atoi(arguments[i]);
| ^~~~~~~~~~~
| history
Vrui/Vislets/FrameRateViewer.cpp:148:28: error: ‘historySize’ was not declared in this scope; did you mean ‘history’?
148 | history=new double[historySize];
| ^~~~~~~~~~~
| history
Vrui/Vislets/FrameRateViewer.cpp: In member function ‘virtual void Vrui::Vislets::FrameRateViewer::frame()’:
Vrui/Vislets/FrameRateViewer.cpp:190:34: error: ‘historySize’ was not declared in this scope; did you mean ‘history’?
190 | for(size_t i=1;i<historySize;++i)
| ^~~~~~~~~~~
| history
Vrui/Vislets/FrameRateViewer.cpp: In member function ‘virtual void Vrui::Vislets::FrameRateViewer::display(GLContextData&) const’:
Vrui/Vislets/FrameRateViewer.cpp:235:53: error: ‘historySize’ was not declared in this scope; did you mean ‘history’?
235 | double xs=double(ds.viewport[2])0.8/double(historySize);
| ^~~~~~~~~~~
| history
make: *** [/home/nadedrm/src/Vrui-8.0-002/BuildRoot/BasicMakefile:224: o/g++-3.g0.O3/pic/Vrui/Vislets/FrameRateViewer.o] Erro 1
make: ** Esperando que outros processos terminem.
Build unsuccessful; please fix any reported errors and try againHow can I fix that?
January 3, 2023 at 11:35 am #2421Sean RobinsonParticipantI suspect you are not using Linux Mint 19, the recommended OS for AR Sandbox. It’s possible to use other OSes, but some changes may be needed for the build process.
Could you post the output of
lsb_release -dc
? The output will tell me what OS version you are using.January 5, 2023 at 9:16 am #2423romulogeoflowParticipantI can’t get the internet working on linux mint 19, it doesn’t work via cable, it doesn’t work via wifi either.
I’m using linux mint 20 “ulyana” but I used the latest one and also stuck on the same error.January 5, 2023 at 10:54 am #2424romulogeoflowParticipantMy bad, I’m late.
I was trying to get it to work.Description: Linux Mint 21.1
Codename: veraJanuary 5, 2023 at 11:22 am #2425Sean RobinsonParticipantNo worries. I just wanted to know the OS version to try to point you in the right direction.
The errors you see are because some things in the compiler changed after LM19 and Vrui has not been updated to handle those changes. If hardware support is an issue, I recommend LM21 over LM20.
See the VRUI – “Unable to locate package” thread for a probable fix.
January 6, 2023 at 1:29 pm #2426marcocspcParticipantI’ve created a Dockerfile that allows building in any Linux distribution that supports docker, take a look at my post in this forum: http://doc-ok.org/?topic=sarndbox-docker
-
AuthorPosts
- You must be logged in to reply to this topic.