 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
For the next scene in my movie, I need to build a bathroom. I want to
do this in povmodeler. The .deb provided doesn't work for me, as I get
blank windows. I thought I'd build it and see if I could debug the
OpenGL failure. But I'm spending too much time just trying to bootstrap
a build.
Has anyone built povmodeler?
I am not familiar with cmake and the instructions are lacking (point to
a dead page).
I loaded CMakeLists.txt in qtcreator. It compiles for a long time and
tips over linking, missing all of the qt libraries. (QApplication,
QEvent, QWidget, QDom, etc)
I don't know how
find_package(Qt5Core REQUIRED)
relates to
target_link_libraries(povmodeler Qt5::Widgets Qt5::Core ...
and why Qt5::Core and Qt5::Widgets are apparently missing after passing
the "REQUIRED" test
--
dik
Rendered 28,677,888,000 of 49,882,521,600 pixels (57%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoft com> wrote:
> Has anyone built povmodeler?
I did.
I don't get anything in the 4 windows either. All the rest is kinda beyond
me...
Probably just a few more small things to fix. 90/10 Rule, and all that.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Dick
I assume you use Linux....
please, in your home directory, give the following commands:
mkdir povmodelerton
cd povmodelerton
git clone https://github.com/eticre/povmodeler.git
cd povmodeler
mkdir build
cd build
cmake ..
make -j4
.../povmodeler
I just tried that here, and it all works. If it doesn't, show the output of
make. Make sure you have those libraries.
Cheers
Ton.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
"Ton" <ton### [at] gmailcom> wrote:
> Hi Dick
>
> I assume you use Linux....
>
> please, in your home directory, give the following commands:
> mkdir povmodelerton
> cd povmodelerton
> git clone https://github.com/eticre/povmodeler.git
> cd povmodeler
> mkdir build
> cd build
> cmake ..
> make -j4
> .../povmodeler
>
> I just tried that here, and it all works. If it doesn't, show the output of
> make. Make sure you have those libraries.
>
> Cheers
> Ton.
Typo alert:
that last line should be
../povmodeler
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/26/19 5:41 PM, Ton wrote:
> Hi Dick
>
> I assume you use Linux....
>
> please, in your home directory, give the following commands:
> mkdir povmodelerton
> cd povmodelerton
> git clone https://github.com/eticre/povmodeler.git
> cd povmodeler
> mkdir build
> cd build
> cmake ..
> make -j4
> .../povmodeler
>
> I just tried that here, and it all works. If it doesn't, show the output of
> make. Make sure you have those libraries.
>
> Cheers
> Ton.
>
>
>
>
/home/dick/povray/github/povmodelerton/povmodeler/pmrendermanager.cpp:48:10:
fatal error: QtX11Extras/QX11Info: No such file or directory
I have that file.
dick@cyd:~/povray/github/povmodelerton/povmodeler/build$ locate QX11Info
/opt/Qt/5.13.1/Src/qtx11extras/include/QtX11Extras/QX11Info
/opt/Qt/5.13.1/gcc_64/include/QtX11Extras/QX11Info
I tried adding
find_package(Qt5X11Extras REQUIRED)
to CMakeLists.txt
but that says
dick@cyd:~/povray/github/povmodelerton/povmodeler/build$ cmake ..
CMake Error at CMakeLists.txt:22 (find_package):
By not providing "FindQt5X11Extras.cmake" in CMAKE_MODULE_PATH this
project
has asked CMake to find a package configuration file provided by
"Qt5X11Extras", but CMake did not find one.
Could not find a package configuration file provided by
"Qt5X11Extras" with
any of the following names:
Qt5X11ExtrasConfig.cmake
qt5x11extras-config.cmake
Add the installation prefix of "Qt5X11Extras" to CMAKE_PREFIX_PATH or set
"Qt5X11Extras_DIR" to a directory containing one of the above files. If
"Qt5X11Extras" provides a separate development package or SDK, be sure it
has been installed.
-- Configuring incomplete, errors occurred!
See also
"/home/dick/povray/github/povmodelerton/povmodeler/build/CMakeFiles/CMakeOutput.log".
--
dik
Rendered 29,374,617,600 of 49,882,521,600 pixels (58%)
Post a reply to this message
Attachments:
Download 'us-ascii' (27 KB)
|
|
| |
| |
|
|
|
|
| |
| |
|
|
I'm a bit surprised that your qt-include directories are in /opt, but that
should not be a problem.
Could you run the next command:
pkg-config --cflags Qt5Core
My output here is:
-DQT_CORE_LIB -I/usr/include/qt5/QtCore -I/usr/include/qt5
and my include file is located at:
/usr/include/qt5/QtX11Extras/QX11Info
So now the compiler knows how to find that file.
The problem with cmake is that you never know the command line of the compiler,
so you don't have a clue about the include directories it's using.
Cheers
Ton.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/27/19 1:40 AM, Ton wrote:
> I'm a bit surprised that your qt-include directories are in /opt, but that
> should not be a problem.
> Could you run the next command:
>
> pkg-config --cflags Qt5Core
>
> My output here is:
> -DQT_CORE_LIB -I/usr/include/qt5/QtCore -I/usr/include/qt5
> and my include file is located at:
> /usr/include/qt5/QtX11Extras/QX11Info
>
> So now the compiler knows how to find that file.
>
> The problem with cmake is that you never know the command line of the compiler,
> so you don't have a clue about the include directories it's using.
Ah ha.
$ pkg-config --cflags Qt5Core
-I/usr/include/x86_64-linux-gnu/qt5/QtCore
-I/usr/include/x86_64-linux-gnu/qt5
qmake knows I want to build with /opt/Qt/5.13.1
cmake does not. It uses the debian installed version, which I think is
5.9.5.
The debian version does not seem to have qt5X11Extras
$ ls /usr/lib/x86_64-linux-gnu/cmake
Qt5 Qt5Concurrent Qt5Core Qt5DBus Qt5Gui Qt5Network
Qt5OpenGLExtensions Qt5PrintSupport Qt5Sql Qt5Test Qt5Widgets Qt5Xml
I don't see a package to install to fix that. There *is* a -doc package
$ apt-cache search qtx11
python-pyqt5.qtx11extras - Python 2 bindings for QtX11Extras module
python-pyqt5.qtx11extras-dbg - Python 2 bindings for QtX11Extras module
(debug extension)
python3-pyqt5.qtx11extras - Python 3 bindings for QtX11Extras module
python3-pyqt5.qtx11extras-dbg - Python 3 bindings for QtX11Extras module
(debug extension)
qtx11extras5-doc - Qt 5 X11 extras documentation
qtx11extras5-doc-html - Qt 5 X11 extras HTML documentation
--
dik
Rendered 29,374,617,600 of 49,882,521,600 pixels (58%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/27/19 3:54 AM, Dick Balaska wrote:
> The debian version does not seem to have qt5X11Extras
> $ ls /usr/lib/x86_64-linux-gnu/cmake
> Qt5 Qt5Concurrent Qt5Core Qt5DBus Qt5Gui Qt5Network
> Qt5OpenGLExtensions Qt5PrintSupport Qt5Sql Qt5Test Qt5Widgets Qt5Xml
>
>
> I don't see a package to install to fix that. There *is* a -doc package
>
> $ apt-cache search qtx11
> python-pyqt5.qtx11extras - Python 2 bindings for QtX11Extras module
> python-pyqt5.qtx11extras-dbg - Python 2 bindings for QtX11Extras module
> (debug extension)
> python3-pyqt5.qtx11extras - Python 3 bindings for QtX11Extras module
> python3-pyqt5.qtx11extras-dbg - Python 3 bindings for QtX11Extras module
> (debug extension)
> qtx11extras5-doc - Qt 5 X11 extras documentation
> qtx11extras5-doc-html - Qt 5 X11 extras HTML documentation
>
found it:
$ sudo apt install libqt5x11extras5-dev
build is progressing...
--
dik
Rendered 29,374,617,600 of 49,882,521,600 pixels (58%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/27/19 4:09 AM, Dick Balaska wrote:
>
> build is progressing...
>
Got it built. I get the same log output as I posted in my previous
thread "povmodeler blank windows".
$ ./povmodeler
qt5ct: using qt5ct plugin
qt5ct: D-Bus global menu: no
Asking for share context for widget that does not have a window handle
QOpenGLWidget: Cannot be used without a context shared with the toplevel.
...
Next I have to get it to build in qtcreator, so I can debug it.
(I have built and run other qt opengl apps.)
--
dik
Rendered 29,374,617,600 of 49,882,521,600 pixels (58%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> On 11/27/19 4:09 AM, Dick Balaska wrote:
>
> >
> > build is progressing...
> >
>
> Got it built. I get the same log output as I posted in my previous
> thread "povmodeler blank windows".
>
> $ ./povmodeler
> qt5ct: using qt5ct plugin
> qt5ct: D-Bus global menu: no
> Asking for share context for widget that does not have a window handle
> QOpenGLWidget: Cannot be used without a context shared with the toplevel.
>
> ...
>
> Next I have to get it to build in qtcreator, so I can debug it.
>
> (I have built and run other qt opengl apps.)
>
> --
> dik
> Rendered 29,374,617,600 of 49,882,521,600 pixels (58%)
Well done, Dick!
Why you don't have the graphics, I don't know. My Qt version here is 5.13, and
it works. It would be hard to imagine 5.13 works, and 5.9 doesn't.
qtcreator uses the same commands (cmake and make) like you used in the
commandline, so that should just work. I'll try later today.
Cheers
Ton.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/27/19 6:55 PM, Ton wrote:
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>> ...
>>
>> Next I have to get it to build in qtcreator, so I can debug it.
>>
>> (I have built and run other qt opengl apps.)
>>
>> --
>> dik
>> Rendered 29,374,617,600 of 49,882,521,600 pixels (58%)
>
> Well done, Dick!
> Why you don't have the graphics, I don't know. My Qt version here is 5.13, and
> it works. It would be hard to imagine 5.13 works, and 5.9 doesn't.
> qtcreator uses the same commands (cmake and make) like you used in the
> commandline, so that should just work. I'll try later today.
>
> Cheers
> Ton.
>
>
>
It built first shot in qtcreator! And it runs fine, go figure.
It's um, very mouse-main-menu oriented. It seems like a lot of work to
do a little.
--
dik
Rendered 29,714,688,000 of 49,882,521,600 pixels (59%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> It built first shot in qtcreator! And it runs fine, go figure.
Can you provide instructions so I can replicate?
> It's um, very mouse-main-menu oriented. It seems like a lot of work to
> do a little.
I figured - but that's why we code. Though some things are very hard to do
_without_ a modeler....
ALSO:
I just did an apt-get upgrade, and while I was helping out jr, I noticed that
qtpovray editor now loses my cursor for a while until I arrow-key up and down.
If I just click on a line, I get a yellow highlight but I have no idea where in
the line the cursor is. :(
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/28/19 10:26 AM, Bald Eagle wrote:
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>
>> It built first shot in qtcreator! And it runs fine, go figure.
>
> Can you provide instructions so I can replicate?
0) make build directory
mkdir ~/povmodelerton
cd ~/povmodelerton
1) Clone his repo
git clone https://github.com/eticre/povmodeler.git
2) Make sure you have cmake
sudo apt install cmake
3) In Qtcreator, enable cmake
Menu -> Tools -> Options
Left Menu - Kits
3a)
Top Tab - CMake
Add
I called mine cmake-3.10.3
Path: /usr/bin/cmake
I have "Autorun cmake" checked.
3b)
Top Tab - Kits
Add
Name: cmake
It should auto-fill in everything else. Important fields:
Device Type: Desktop
CMake Tool: (The one you just created in the cmake tab)
OK to put this mess away
4)
Menu -> Open File
~/povmodelerton/povmodeler/CMakeLists.txt
This takes you to the "Projects" screen.
All of the "Build and Run" options are dimmed out.
Click on "cmake" to enable it.
This will create a slew of text boxes for options, and it should
auto-fill the bulk of them.
This is done. There is no "OK" to put it away.
5)
Now, in the grey strip on the far left of the window, click the Edit
button (Above Design). Note the project "qt5-pov".
On the bottom of the grey strip, the monitor icon is surrounded with
"qt5-pov" "Debug"
6)
Build it. Type ^B to build or if you're really brave ^R to build and run :)
The bottom strip buttons "4 Compile Output" will let you follow along.
7)
Go get a beer. Or two. This takes a while.
>
>> It's um, very mouse-main-menu oriented. It seems like a lot of work to
>> do a little.
>
> I figured - but that's why we code. Though some things are very hard to do
> _without_ a modeler....
Agreed. But, I'm not seeing any particular benefit to this modeler.
It's a great start, but for me it needs
1. Tree Editor to easily rearrange the nodes in the tree.
2. Better context menus in the tree.
I want to right click in the tree, "Insert -> Simple shapes -> Box"
3. Filtered menus.
Right now every option is always present. So there are a 1000 menu
entries with "Pigment" buried in the 23rd menu of the 23rd menu. If I'm
on a "texture" node in the tree, I don't need "Global Settings", I need
"Pigment".
4. Resize object by click-drag in the modeler windows.
(Grabbing in the Camera view would be hard, but Top/Left/Front views
should be easy)
5. Highlight the current object when selected in the tree.
6. A bug. "Render" launches /usr/bin/povray and it and its window just
stay when it's done. One must go to the shell and kill it to terminate it.
7. Hotkeys. I want ^R to render, etc.
>
>
> ALSO:
> I just did an apt-get upgrade, and while I was helping out jr, I noticed that
> qtpovray editor now loses my cursor for a while until I arrow-key up and down.
> If I just click on a line, I get a yellow highlight but I have no idea where in
> the line the cursor is. :(
This is driving me crazy. I was gonna ask if you started seeing it too.
I am to the point where I need to ask on Qt forums "wtf?".
>
>
--
dik
Rendered 29,795,558,400 of 49,882,521,600 pixels (59%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> 3) In Qtcreator, enable cmake
> Menu -> Tools -> Options
> Left Menu - Kits
Hmmm. I have 3.5.1 I don't see this and that following stuff.
> This is driving me crazy. I was gonna ask if you started seeing it too.
> I am to the point where I need to ask on Qt forums "wtf?".
I was wondering if you were seeing it or had somehow glossed over it.
No breaky the Qt.
If you're gonna ask, I'd love to see the render button moved to somewhere over
the text-editing region (I let the rest of the stuff hang off-screen), and maybe
have the render window gain focus on starting a new render.
Go eat.
Happy Thanksgiving :)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/28/19 5:06 PM, Bald Eagle wrote:
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>
> If you're gonna ask, I'd love to see the render button moved to somewhere over
> the text-editing region (I let the rest of the stuff hang off-screen),
Press ^R to start a render?
> and maybe
> have the render window gain focus on starting a new render.
So, you have the Render window set to not-always-on-top and you want it
to pop on top when you start a render?
Hey Jr, are you still using qtpovray? Do you see this missing text
I-beam nonsense with slakware? (BE and I are both Mint; a sample size
of 1.)
--
dik
Rendered 39,329,971,200 of 49,882,521,600 pixels (78%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Dick Balaska <dic### [at] buckosoftcom> wrote:
> On 11/28/19 5:06 PM, Bald Eagle wrote:
> > ...
> Hey Jr, are you still using qtpovray? Do you see this missing text
> I-beam nonsense with slakware? (BE and I are both Mint; a sample size
> of 1.)
v quick try (haven't really gotten into using it yet[*]). no, I do not see the
"I-beam nonsense" :-) (Slackware. reliable. ;-)) switching focus between
panes, always get the insertion thing; line highlighting too works as it should.
v 3.80.0, built mid July last year.
[*] if you could integrate eticre's code base with qtpovray, _that_ would change
everything. :-)
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 12/3/19 4:54 AM, jr wrote:
> hi,
>
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>> On 11/28/19 5:06 PM, Bald Eagle wrote:
>>> ...
>> Hey Jr, are you still using qtpovray? Do you see this missing text
>> I-beam nonsense with slakware? (BE and I are both Mint; a sample size
>> of 1.)
>
> v quick try (haven't really gotten into using it yet[*]). no, I do not see the
> "I-beam nonsense" :-) (Slackware. reliable. ;-)) switching focus between
> panes, always get the insertion thing; line highlighting too works as it should.
> v 3.80.0, built mid July last year.
Yeah, I expect that one to work. It's something recent that made it go
kablooey. It's hard because I switched from Ubuntu to Mint at about the
same time I noticed it.
>
> [*] if you could integrate eticre's code base with qtpovray, _that_ would change
> everything. :-)
I played with this a bit more. It's not as bad as I originally thought.
I built a bathtub in it.
I'm thinking of two changes to it.
1) Integrate povrayws, my websocket povray. Right now, he calls
/usr/bin/povray lots, waits for user to terminate it, and reads the
results. povmodeler *could* just display the texture preview, rather
than go through those hoops to get it.
Or, I have libpovray.a built. Maybe I should use that. (That would be
trickier because I'd need to make a public API out of the VFE in the pov
source tree.)
2) Exporting SDL is primitive. Right now, after exporting a scene, one
must cut/paste the useful object into their own code. I want
#declare Bathtub=union {...}
and then be able to use that file directly.
My files are organized so that I can either render them directly, or
include them in another file:
bathtub.inc
#version 3.7;
#ifndef (True)
#declare True=1;
#declare BATHTUBINC_TEST=1;
camera { blah blah }
light_source { test lights }
#end
#declare Bathtub = union {}
#ifdef (BATHTUBINC_TEST)
object {Bathtub}
#end
>
> regards, jr.
>
>
--
dik
Rendered 40,182,220,800 of 49,882,521,600 pixels (80%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Hi Dick, if you edit pmpovrayrenderwidget.cpp, and change the +D and +P into -D
and -P (line 122), povray doesn't show the render window, and it doesn't pause.
That whole messagebox for changing the arguments could be removed as well, not
very useful.
I assume you know that you have to recompile povmodeler. Changing the text file
by itself is not enough.....
To copy one object into a text file, you can just select that particular object,
press Ctrl-C, and then in the text file Ctrl-V, and that object appears,
magically, in your text.
Cheers
Ton.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Dick Balaska <dic### [at] buckosoftcom> wrote:
> On 12/3/19 4:54 AM, jr wrote:
> > Dick Balaska <dic### [at] buckosoftcom> wrote:
> >> On 11/28/19 5:06 PM, Bald Eagle wrote:
> >>> ...
> >> Hey Jr, are you still using qtpovray? Do you see this missing text
> >> I-beam nonsense with slakware? (BE and I are both Mint; a sample size
> >> of 1.)
> >
> > v quick try (haven't really gotten into using it yet[*]). no, I do not see the
> > "I-beam nonsense" :-) (Slackware. reliable. ;-)) switching focus between
> > panes, always get the insertion thing; line highlighting too works as it should.
> > v 3.80.0, built mid July last year.
>
> Yeah, I expect that one to work. It's something recent that made it go
> kablooey. It's hard because I switched from Ubuntu to Mint at about the
> same time I noticed it.
>
> > [*] if you could integrate eticre's code base with qtpovray, _that_ would change
> > everything. :-)
>
> I played with this a bit more. It's not as bad as I originally thought.
> I built a bathtub in it.
>
> I'm thinking of two changes to it.
> 1) Integrate povrayws, my websocket povray. Right now, he calls
> /usr/bin/povray lots, waits for user to terminate it, and reads the
> results. povmodeler *could* just display the texture preview, rather
> than go through those hoops to get it.
>
> Or, I have libpovray.a built. Maybe I should use that. (That would be
> trickier because I'd need to make a public API out of the VFE in the pov
> source tree.)
>
> 2) Exporting SDL is primitive. Right now, after exporting a scene, one
> must cut/paste the useful object into their own code. I want
> #declare Bathtub=union {...}
> and then be able to use that file directly.
looks to me like Ton's copy+paste info indicates that integration (sorry to bang
on about it) with you own editor should be straightforward. I really think that
a single UI/frontend would work.
> My files are organized so that I can either render them directly, or
> include them in another file:
I've started having '#if (0) ... #end' guards around each scene element, and
switch most things off while tuning some bit. crazy. :-)
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11/28/19 10:26 AM, also sprach Bald Eagle:
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>
>> It built first shot in qtcreator! And it runs fine, go figure.
>
> Can you provide instructions so I can replicate?
Hey Baldy, try this:
sudo apt install libfreetype6 libfreetype6-dev
sudo apt install libqt5x11extras5
sudo apt install libqt5x11extras5-dev
sudo apt install libqt5opengl5
sudo apt install libqt5opengl5-dev
cd goodplace
mkdir qtpovmodeler
cd qtpovmodeler
git clone https://github.com/dickbalaska/qtpovmodeler.git
cd qtpovmodeler
qmake
make -j4
(get a beer)
./qtpovmodeler
That's what I had to install extra to get it to build. (And I made a
qmake file). I don't know if I had other things installed already that
you don't. Let me know.
I renamed my clone of the project because I want to make a .deb and
there is already a povmodeler.deb .
--
dik
Rendered 42,162,508,800 of 49,882,521,600 pixels (84%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 12/4/19 6:12 AM, also sprach Ton:
> Hi Dick, if you edit pmpovrayrenderwidget.cpp, and change the +D and +P into -D
> and -P (line 122), povray doesn't show the render window, and it doesn't pause.
> That whole messagebox for changing the arguments could be removed as well, not
> very useful.
> I assume you know that you have to recompile povmodeler. Changing the text file
> by itself is not enough.....
> To copy one object into a text file, you can just select that particular object,
> press Ctrl-C, and then in the text file Ctrl-V, and that object appears,
> magically, in your text.
>
> Cheers
> Ton.
Hoy! Mr Ton.
Those are both very useful tips. Thank you!
Agreed about getting rid of the useless MessageBox.
--
dik
Rendered 42,220,569,600 of 49,882,521,600 pixels (84%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Thanks - I only needed 2 of the -dev packages, but probably need one or two more
things to get this to work smoothly.
Here's what happened.
I'm thinking it's just an edit in the make file to append '-std=c++11' to the
compiler command?
qtpovmodeler $ make -j4
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS
-DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB
-DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I. -isystem /usr/include/freetype2
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o main.o src/main.cpp
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS
-DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB
-DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I. -isystem /usr/include/freetype2
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o pm2dcontrolpoint.o
src/pm2dcontrolpoint.cpp
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS
-DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB
-DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I. -isystem /usr/include/freetype2
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o pm3dcontrolpoint.o
src/pm3dcontrolpoint.cpp
g++ -c -m64 -pipe -O2 -Wall -W -D_REENTRANT -fPIC -DQT_DEPRECATED_WARNINGS
-DQT_NO_DEBUG -DQT_OPENGL_LIB -DQT_WIDGETS_LIB -DQT_X11EXTRAS_LIB -DQT_GUI_LIB
-DQT_XML_LIB -DQT_DBUS_LIB -DQT_CORE_LIB -I. -I. -isystem /usr/include/freetype2
-isystem /usr/include/x86_64-linux-gnu/qt5 -isystem
/usr/include/x86_64-linux-gnu/qt5/QtOpenGL -isystem
/usr/include/x86_64-linux-gnu/qt5/QtWidgets -isystem
/usr/include/x86_64-linux-gnu/qt5/QtX11Extras -isystem
/usr/include/x86_64-linux-gnu/qt5/QtGui -isystem
/usr/include/x86_64-linux-gnu/qt5/QtXml -isystem
/usr/include/x86_64-linux-gnu/qt5/QtDBus -isystem
/usr/include/x86_64-linux-gnu/qt5/QtCore -I.
-I/usr/lib/x86_64-linux-gnu/qt5/mkspecs/linux-g++-64 -o pmactions.o
src/pmactions.cpp
src/pm2dcontrolpoint.cpp:31:4: warning: identifier ‘nullptr’ is a keyword in
C++11 [-Wc++0x-compat]
m_pBasePoint = nullptr;
^
src/pm2dcontrolpoint.cpp: In constructor
‘PM2DControlPoint::PM2DControlPoint(const PMVector&, PM2DControlPoint::CPType,
int, const QString&)’:
src/pm2dcontrolpoint.cpp:31:19: error: ‘nullptr’ was not declared in this scope
m_pBasePoint = nullptr;
^
In file included from src/pmshell.h:23:0,
from src/main.cpp:23:
src/pmdockwidget.h:319:5: warning: identifier ‘nullptr’ is a keyword in C++11
[-Wc++0x-compat]
PMDockTabGroup( QWidget *parent = nullptr )
^
src/pmactions.cpp:33:4: warning: defaulted and deleted functions only available
with -std=c++11 or -std=gnu++11
= default;
^
make: *** [Makefile:4912: pm2dcontrolpoint.o] Error 1
make: *** Waiting for unfinished jobs....
src/pmdockwidget.h:319:39: error: ‘nullptr’ was not declared in this scope
PMDockTabGroup( QWidget *parent = nullptr )
^
In file included from src/pmshell.h:23:0,
from src/main.cpp:23:
src/pmdockwidget.h:393:64: error: ‘nullptr’ was not declared in this scope
const QPixmap &pixmap, QWidget* parent = nullptr, const Q
^
src/pmdockwidget.h:1167:41: error: ‘nullptr’ was not declared in this scope
PMDockMainWindow( QWidget* parent = nullptr, Qt::WindowFlags f = nullptr/*
^
src/pmdockwidget.h:1167:70: error: ‘nullptr’ was not declared in this scope
PMDockMainWindow( QWidget* parent = nullptr, Qt::WindowFlags f = nullptr/* |
^
src/pmdockwidget.h:1210:78: error: ‘nullptr’ was not declared in this scope
DockWidget* createDockWidget( const QPixmap &pixmap, QWidget* parent = nullptr,
^
In file included from src/pmglview.h:39:0,
from src/pmshell.h:26,
from src/main.cpp:23:
src/pmviewbase.h:96:54: error: ‘nullptr’ was not declared in this scope
PMViewBase( QWidget* parent, Qt::WindowFlags f = nullptr )
^
In file included from src/pmobjectaction.h:27:0,
from src/pmglview.h:44,
from src/pmshell.h:26,
from src/main.cpp:23:
src/pmmetaobject.h:359:71: error: ‘nullptr’ was not declared in this scope
PMMetaObject( const QString& className, PMMetaObject* superClass = nullptr,
^
src/pmmetaobject.h:360:56: error: ‘nullptr’ was not declared in this scope
PMObjectFactoryMethod factoryMethod = nullptr );
^
src/pmmetaobject.h: In member function ‘bool PMMetaObject::isAbstract() const’:
src/pmmetaobject.h:382:50: error: ‘nullptr’ was not declared in this scope
bool isAbstract() const { return m_factory == nullptr; }
^
src/pmmetaobject.h: In member function ‘PMPropertyBase*
PMMetaObject::property(const QString&) const’:
src/pmmetaobject.h:401:51: error: ‘nullptr’ was not declared in this scope
if( it == m_propertiesDict.end() ) return nullptr;
^
In file included from src/pmshell.h:26:0,
from src/main.cpp:23:
src/pmglview.h: At global scope:
src/pmglview.h:70:32: error: ‘nullptr’ was not declared in this scope
QWidget* parent = nullptr, Qt::WindowFlags f = nullptr );
^
src/pmglview.h:70:61: error: ‘nullptr’ was not declared in this scope
QWidget* parent = nullptr, Qt::WindowFlags f = nullptr );
^
src/pmglview.h: In member function ‘virtual PMViewBase*
PMGLViewFactory::newInstance(QWidget*, PMPart*) const’:
src/pmglview.h:555:63: error: call to ‘PMGLView::PMGLView(PMPart*,
PMGLView::PMViewType, QWidget*, Qt::WindowFlags)’ uses the default argument for
parameter 4, which is not yet defined
return new PMGLView( part, PMGLView::PMViewPosX, parent );
^
In file included from src/main.cpp:23:0:
src/pmshell.h: At global scope:
src/pmshell.h:144:67: error: ‘nullptr’ was not declared in this scope
PMDockWidget* createView( const QString& t, PMViewOptions* c = nullptr,
^
In file included from src/pmrendermanager.h:26:0,
from src/main.cpp:24:
src/pmobject.h:157:57: error: ‘nullptr’ was not declared in this scope
const PMObjectList* objectsBetween = nullptr ) const;
^
src/pmobject.h:166:57: error: ‘nullptr’ was not declared in this scope
const PMObjectList* objectsBetween = nullptr ) const;
^
src/pmobject.h: In member function ‘PMTreeViewItem* PMObject::getTreeItem()’:
src/pmobject.h:60:82: error: ‘nullptr’ was not declared in this scope
wItem* getTreeItem() { if ( pmt_item ) return pmt_item; else return nullptr; }
^
src/pmobject.h: In member function ‘virtual PMObject* PMObject::firstChild()
const’:
src/pmobject.h:185:50: error: ‘nullptr’ was not declared in this scope
virtual PMObject* firstChild() const { return nullptr; }
^
src/pmobject.h: In member function ‘virtual PMObject* PMObject::lastChild()
const’:
src/pmobject.h:189:49: error: ‘nullptr’ was not declared in this scope
virtual PMObject* lastChild() const { return nullptr; }
^
src/pmobject.h: In member function ‘virtual PMObject* PMObject::childAt(uint)
const’:
src/pmobject.h:194:53: error: ‘nullptr’ was not declared in this scope
virtual PMObject* childAt( uint ) const { return nullptr; }
^
src/pmobject.h: In member function ‘virtual PMViewStructure*
PMObject::viewStructure()’:
src/pmobject.h:298:54: error: ‘nullptr’ was not declared in this scope
virtual PMViewStructure* viewStructure() { return nullptr; }
^
src/pmobject.h: In member function ‘virtual PMDeclare* PMObject::linkedObject()
const’:
src/pmobject.h:443:53: error: ‘nullptr’ was not declared in this scope
virtual PMDeclare* linkedObject() const { return nullptr; }
^
src/pmobject.h: In member function ‘bool PMObject::mementoCreated() const’:
src/pmobject.h:467:55: error: ‘nullptr’ was not declared in this scope
bool mementoCreated() const { return m_pMemento != nullptr; }
^
In file included from src/main.cpp:24:0:
src/pmrendermanager.h: At global scope:
src/pmrendermanager.h:261:40: error: ‘nullptr’ was not declared in this scope
PMRenderManager( QWidget *parent = nullptr );
^
src/main.cpp: In function ‘int main(int, char**)’:
src/main.cpp:29:21: error: ‘nullptr’ was not declared in this scope
PMShell* shell = nullptr;
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Dick Balaska <dic### [at] buckosoftcom> wrote:
> Am 11/28/19 10:26 AM, also sprach Bald Eagle:
> > Dick Balaska <dic### [at] buckosoftcom> wrote:
> >> It built first shot in qtcreator! And it runs fine, go figure.
> > Can you provide instructions so I can replicate?
>
> Hey Baldy, try this:
> ...
instructions work. even for people with hair. :-) minor problem, it complains
(on startup): Rule file 'povmodeler/ "baseinsertrules.xml" ' not found. the
file does exist though.
then five "Asking for share context for widget..." warnings/errors, followed by
a number of "QMainWindow::saveState(): 'objectName' not set for QToolBar", each
with a different pointer/address (one per button?).
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 12/7/19 8:44 AM, also sprach Bald Eagle:
>
> I'm thinking it's just an edit in the make file to append '-std=c++11' to the
> compiler command?
make clean
git pull
qmake
make -j4
--
dik
Rendered 43,099,776,000 of 49,882,521,600 pixels (86%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
OK, that seemed to work "better."
Got a bunch of the usual stuff, some
warning: unused parameter ‘foo, bar, etc’ [-Wunused-parameter]
and then
src/pmpart.cpp: In member function ‘void PMPart::initActions()’:
src/pmpart.cpp:380:42: error: no matching function for call to
‘QAction::QAction(const char [7])’
m_pImportAction = new
QAction("Import");//m_pShell->get_fileMenu()->addAction( "Import" );
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmenu.h:40:0,
from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMenu:1,
from src/pmshell.h:29,
from src/pmpart.cpp:23:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:174:5: note: candidate:
QAction::QAction(QActionPrivate&, QObject*)
QAction(QActionPrivate &dd, QObject *parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:174:5: note: candidate
expects 2 arguments, 1 provided
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:89:5: note: candidate:
QAction::QAction(const QIcon&, const QString&, QObject*)
QAction(const QIcon &icon, const QString &text, QObject* parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:89:5: note: candidate
expects 3 arguments, 1 provided
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:88:5: note: candidate:
QAction::QAction(const QString&, QObject*)
QAction(const QString &text, QObject* parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:88:5: note: candidate
expects 2 arguments, 1 provided
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:87:14: note: candidate:
QAction::QAction(QObject*)
explicit QAction(QObject* parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:87:14: note: no known
conversion for argument 1 from ‘const char [7]’ to ‘QObject*’
src/pmpart.cpp:384:42: error: no matching function for call to
‘QAction::QAction(const char [7])’
m_pExportAction = new QAction("Export");
^
In file included from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/qmenu.h:40:0,
from /usr/include/x86_64-linux-gnu/qt5/QtWidgets/QMenu:1,
from src/pmshell.h:29,
from src/pmpart.cpp:23:
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:174:5: note: candidate:
QAction::QAction(QActionPrivate&, QObject*)
QAction(QActionPrivate &dd, QObject *parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:174:5: note: candidate
expects 2 arguments, 1 provided
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:89:5: note: candidate:
QAction::QAction(const QIcon&, const QString&, QObject*)
QAction(const QIcon &icon, const QString &text, QObject* parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:89:5: note: candidate
expects 3 arguments, 1 provided
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:88:5: note: candidate:
QAction::QAction(const QString&, QObject*)
QAction(const QString &text, QObject* parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:88:5: note: candidate
expects 2 arguments, 1 provided
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:87:14: note: candidate:
QAction::QAction(QObject*)
explicit QAction(QObject* parent);
^
/usr/include/x86_64-linux-gnu/qt5/QtWidgets/qaction.h:87:14: note: no known
conversion for argument 1 from ‘const char [7]’ to ‘QObject*’
make: *** [Makefile:9649: pmpart.o] Error 1
make: *** Waiting for unfinished jobs....
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 12/7/19 4:53 PM, also sprach Bald Eagle:
> Dick Balaska <dic### [at] buckosoftcom> wrote:
>
> OK, that seemed to work "better."
>
Well, forget that.
I just built this one and it has the failed OpenGL init nonsense.
I'll have to unwind where I killed it.
--
dik
Rendered 43,456,435,200 of 49,882,521,600 pixels (87%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 12/7/19 8:38 PM, also sprach Dick Balaska:
>
> Well, forget that.
> I just built this one and it has the failed OpenGL init nonsense.
> I'll have to unwind where I killed it.
I can't get it to work with the debian/ubuntu/mint default Qt version of
5.9.5. (I'm still working on it) It works fine with Qt 5.13.1.
I'm curious if this works. Try this.
I assume you installed povmodeler-1.1.4-linuxmint-19.2.deb so that all
of the support files are in the right place.
This is a built binary that works on my machine. It's all static linked
so it *should* run for you.
wget http://www.buckosoft.com/tmp/qtpovmodeler.bz2
bunzip2 qtpovmodeler.bz2
chmod +x qtpovmodeler
./qtpovmodeler
--
dik
Rendered 44,001,792,000 of 49,882,521,600 pixels (88%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Dick Balaska <dic### [at] buckosoftcom> wrote:
> I assume you installed povmodeler-1.1.4-linuxmint-19.2.deb so that all
> of the support files are in the right place.
or not ;)
> wget http://www.buckosoft.com/tmp/qtpovmodeler.bz2
> bunzip2 qtpovmodeler.bz2
> chmod +x qtpovmodeler
> ./qtpovmodeler
qtpovmodeler $ ./qtpovmodeler
../qtpovmodeler: /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5: version `Qt_5' not
found (required by ./qtpovmodeler)
../qtpovmodeler: /usr/lib/x86_64-linux-gnu/libQt5Gui.so.5: version `Qt_5' not
found (required by ./qtpovmodeler)
../qtpovmodeler: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5.13' not
found (required by ./qtpovmodeler)
../qtpovmodeler: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version `Qt_5' not
found (required by ./qtpovmodeler)
../qtpovmodeler: /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5: version `Qt_5' not
found (required by ./qtpovmodeler)
../qtpovmodeler: /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5: version `Qt_5' not
found (required by ./qtpovmodeler)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
>
> Hoy! Mr Ton.
>
> Those are both very useful tips. Thank you!
>
> Agreed about getting rid of the useless MessageBox.
>
>
> --
> dik
> Rendered 42,220,569,600 of 49,882,521,600 pixels (84%)
Hello Dick, you can skip that mr. I'm just Ton!
If you replace this code in pmpovrayrenderwidget.cpp
//eticre add +D +P for preview png default format +FP
m_args = m_args + QString( "+I" ) + m_pTempFile->fileName() + " +O-" + "
+FP"
+ "\n" + " -D" + " -P";
QFileInfo file_info( documentURL.toString() );
if( !documentURL.isEmpty() && documentURL.isLocalFile() )
{
m_pProcess->setWorkingDirectory( file_info.path().remove( 0, 6 ) );
}
m_progress = 0;
m_bPixmapUpToDate = false;
//get user input modify args
// QInputDialog qi;
// qi.setInputMode( QInputDialog::TextInput );
// qi.setOptions( QInputDialog::UsePlainTextEditForTextInput );
// m_args = qi.getMultiLineText( this, "povray", "
______________________cmdline____________________
",
// m_args, nullptr, Qt::Widget,
Qt::ImhMultiLine );
that messagebox is gone. Also those arguments for creating a movie are gone.
Cheers
Ton.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 12/10/19 1:18 AM, also sprach jr:
>
> btw, re 'qtpovmodeler', what's with the baseinsertrules.xml file not
found?
> (same for the docmap xml).
Did you do make install? I got these installed from the povmodeler.deb
file.
$ ls /usr/share/povmodeler/
baseinsertrules.xml examples library povraydocmap.xml questionmark.png
I would guess you have the same in /usr/local?
But. I did not set up make install in the qmake file yet. You would
have had to have done that from the povmodeler's cmake.
> also, and that may be my window manager to blame
> (WindowMaker 0.95.7), main menu accelerator key bindings do not work
for me.
They don't work for me either.
--
dik
Rendered 49,882,521,600 of 49,882,521,600 pixels (100%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
hi,
Dick Balaska <dic### [at] buckosoftcom> wrote:
> Am 12/10/19 1:18 AM, also sprach jr:
> > btw, re 'qtpovmodeler', what's with the baseinsertrules.xml file not
> found?
> > (same for the docmap xml).
>
> Did you do make install? I got these installed from the povmodeler.deb
> file.
> $ ls /usr/share/povmodeler/
> baseinsertrules.xml examples library povraydocmap.xml questionmark.png
>
> I would guess you have the same in /usr/local?
not quite. I only built the executable, then tried it in-situ (temp build dir);
both the exe and the supporting xml were in the same directory though.
> But. I did not set up make install in the qmake file yet. You would
> have had to have done that from the povmodeler's cmake.
will you be adding the install procedure in the near future?
> > also, and that may be my window manager to blame
> > (WindowMaker 0.95.7), main menu accelerator key bindings do not work
> for me.
>
> They don't work for me either.
not my setup then, ok. another "not working for me" item is the preferences
dialog, afaict it does not save changed setting between sessions.
(how did you manage to create a bathtub, _anything_??)
regards, jr.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 12/11/19 11:00 AM, also sprach jr:
>
>
> (how did you manage to create a bathtub, _anything_??)
I installed the .deb, which I think put all of the right files in place.
The exe in the .deb doesn't work.
I got it to build and run fine in qtcreator using Qt 5.13.1
It suffers the OpenGL init errors if I build it under Qt 5.9 (the
current debian version).
It's weird that it requires such a new version of Qt, since the program
was ported from Qt 3.
--
dik
Rendered 49,882,521,600 of 49,882,521,600 pixels (100%)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
|
|
