Closed GoogleCodeExporter closed 8 years ago
The setOpacity method was added in Qt 4.5. If you don't want to upgrade Qt,
then
deleting line 107 in src/mainviewer.cpp should allow it to compile. I should
have
checked this before making a release since it's obviously not compatible with
Qt 4.3.
Original comment by bit...@gmail.com
on 13 Apr 2009 at 11:02
after commenting out line 107 I get this error message.
./build.sh
Building Qosmic
Project MESSAGE: Generating Makefile for Qosmic version 1.4.4
Project MESSAGE: Qt version : 4.3.4
Project MESSAGE: Default number of rendering threads : 2
Project MESSAGE: Location of flam3-palettes.xml : /usr/local/share/flam3
g++ -c -pipe -fpermissive -O2 -D_REENTRANT -w -DPNG_NO_MMX_CODE
-I/usr/local/include
-I/usr/include/libpng12 -I/usr/include/libxml2 -DQT_SHARED -DNTHREADS=2
-DNAMEVER='"version 1.4.4"' -DFLAM3DIR='"/usr/local/share/flam3"'
-DSHAREDIR='"/usr/share"' -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB
-I/usr/share/qt4/mkspecs/linux-g++ -I. -I/usr/include/qt4/QtCore
-I/usr/include/qt4/QtCore -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtGui
-I/usr/include/qt4 -I/usr/include/lua5.1 -Isrc -I.moc -I.ui -o
.obj/doublevalueeditor.o src/doublevalueeditor.cpp
src/doublevalueeditor.cpp: In member function ‘virtual void
DoubleValueEditor::mousePressEvent(QMouseEvent*)’:
src/doublevalueeditor.cpp:84: error: ‘class QMouseEvent’ has no member
named ‘posF’
src/doublevalueeditor.cpp: In member function ‘virtual void
DoubleValueEditor::mouseMoveEvent(QMouseEvent*)’:
src/doublevalueeditor.cpp:95: error: ‘class QMouseEvent’ has no member
named ‘posF’
make: *** [.obj/doublevalueeditor.o] Error 1
error while building qosmic
Original comment by deefacto...@gmail.com
on 14 Apr 2009 at 5:45
This one was introduced in Qt 4.4, but using pos() instead of posF() seems to
work
fine. I've attached a patch if you want to try once more. Thank you for
helping me
find the actual dependency version of Qt.
Original comment by bit...@gmail.com
on 14 Apr 2009 at 10:55
Attachments:
I've installed the Qt. 4.5 by building the source
http://www.qtsoftware.com/downloads/linux-x11-cpp (it took 5 hours to compile).
After
that it continued to compile qosmic but ran into this error attached.
Original comment by deefacto...@gmail.com
on 15 Apr 2009 at 4:42
Attachments:
On the line that starts with g++ in your error message there should be an
option -llua
added to that command, but it's not there. You can edit the qosmic.pro file to
try
and resolve this, or you can cut and paste that line from your error message
and add
the -llua option to the end yourself.
If you want to adjust the qosmic.pro file then remove lua from the PKGCONFIG
variable,
and adjust the LIBS and INCLUDEPATH according to your setup so it will find
liblua.
Original comment by bit...@gmail.com
on 15 Apr 2009 at 10:14
It compiled with -llua5.1 added to the LIBS var in qosmic.pro
Thanks for the support.
Original comment by deefacto...@gmail.com
on 15 Apr 2009 at 11:30
I have two words for the coders out there;
"INSTALL BUTTON"
Original comment by harlequi...@yahoo.com
on 31 May 2009 at 10:34
here is a clipped version of my build return.
Package libxml-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `libxml-2.0.pc'
to the PKG_CONFIG_PATH environment variable
and
Package lua was not found in the pkg-config search path.
Perhaps you should add the directory containing `lua.pc'
to the PKG_CONFIG_PATH environment variable
I have no idea where to put these paths in the qosmic.pro file.
Help please.
Original comment by harlequi...@yahoo.com
on 31 May 2009 at 10:42
It would be nice to have some help with this.
Original comment by harlequi...@yahoo.com
on 31 May 2009 at 11:02
since there is no email notification option here, maybe someone could email me
when
you get around to helping me out on this.
harlequingraphics@yahoo.com
Original comment by harlequi...@yahoo.com
on 31 May 2009 at 11:19
Does the last item in the FAQ section of the BuildAndInstall wiki page not
help? It
looks like you are having the same problem. I'm assuming that you were able to
install flam3 correctly?
BTW, there is an email notification for items in the issues section. I can
appreciate
your frustration, but some of the comments you've left haven't encouraged me to
reply.
I know it's a pain, but your are trying to make the "Install Button" for your
system
since the people who created your distribution haven't yet made one.
You can also file a bug with your distribution asking them to include a package
for
Qosmic. You won't have to compile, but it may take some time for them to
respond.
Original comment by bit...@gmail.com
on 1 Jun 2009 at 12:10
the FAQ section didn't help. I have flam3 installed correctly now but I don't
know
how to edit the qosmic.pro file. I most likely will have the same problem when
it
comes to LUA.
Original comment by harlequi...@yahoo.com
on 1 Jun 2009 at 12:36
Any help on this at all?
Original comment by harlequi...@yahoo.com
on 1 Jun 2009 at 1:59
WOW, this is pretty damn lame.
Original comment by harlequi...@yahoo.com
on 1 Jun 2009 at 4:50
What version of flam3 do you have installed ? and what version of qosmic are you
installing?
Original comment by deefacto...@gmail.com
on 1 Jun 2009 at 5:34
I installed the latest version of both.
Original comment by harlequi...@yahoo.com
on 2 Jun 2009 at 1:55
do you have Qt. 4.5 ?
Original comment by deefacto...@gmail.com
on 2 Jun 2009 at 3:22
sudo apt-get install liblua5.1-0-dev zlib1g-dev libpng12-dev libxml2-dev
libjpeg62-dev
build qt 4.5 from source if you cannot find the package. (sudo apt-cache show
qt5-dev-tools)
http://www.qtsoftware.com/downloads/linux-x11-cpp
Original comment by deefacto...@gmail.com
on 2 Jun 2009 at 3:34
and installing those files will edit qosmic.pro for me?
Original comment by harlequi...@yahoo.com
on 2 Jun 2009 at 5:39
I have qt
Original comment by harlequi...@yahoo.com
on 2 Jun 2009 at 5:51
This is really lame. Way to go. Thanks for the help.
Original comment by harlequi...@yahoo.com
on 3 Jun 2009 at 9:54
Original comment by bit...@gmail.com
on 4 Jun 2009 at 1:02
Original issue reported on code.google.com by
deefacto...@gmail.com
on 8 Apr 2009 at 6:09