thanks for the reply - I will give it a go with the geenral list and use osgQT
in the subject line to make it easy to see.
Cheers,
Paul
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=69409#69409
___
I would say it's good to have OSG related info in one place.
2016-11-15 19:25 GMT+07:00 Robert Osfield :
> On 15 November 2016 at 10:37, Paul McIntosh
> wrote:
> > Should osgQT have it's own section in the forums?
>
> This is a decision for the community/forum moderators.
>
> I am not a forum us
On 15 November 2016 at 10:37, Paul McIntosh
wrote:
> Should osgQT have it's own section in the forums?
This is a decision for the community/forum moderators.
I am not a forum user or moderator so don't have any direct input or
exposure to how it is used. I can see value in have a osgQt section
Hi Robert,
Should osgQT have it's own section in the forums?
I keep coming back to this thread for updates while I am trying to get it to
work myself on Windows 10. I am eager to contribute but it is bit hard not
having an area to post and answer osgQT related issues.
Cheers,
Paul
---
Hi Mathieu,
Here is a summary of what I did to get it to compile in MSVC 2015.
at line 130 where is says
SET(OPENSCENEGRAPH_SOVERSION 145)
add the following lines that set the version numbers
SET(OPENSCENEGRAPH_MAJOR_VERSION 3)
SET(OPENSCENEGRAPH_MINOR_VERSION 5)
SET(OPENSCENEGRAPH_PATCH_VERS
I'll look into that thanks for the update
Le lun. 17 oct. 2016 à 13:04, Stev Kookmal a écrit :
> Hey all,
>
> When building with MSVC2015 and WIN32. CMAKE throws am error at this line
>
> INCLUDE(Find3rdPartyDependencies)
>
> This probably shouldnt be there anymore and is artifact from the origi
Hey all,
When building with MSVC2015 and WIN32. CMAKE throws am error at this line
INCLUDE(Find3rdPartyDependencies)
This probably shouldnt be there anymore and is artifact from the original OSG
.cmake. Deleting it makes things run fine again and CMAKE configures and
generates without an
Hi Mathieu,
One other thing that is also not any sort of priority or
any sort of bug report for you to concern yourself with, but
maybe you know something about it with your work on this
project.
The attached PIC to this reply is what I get when starting
the osgviewerQt example. You will notice
Hi Mathieu,
I did a pull on osg and osgQt just to make sure I had the
latest of both.
cmake on osgQt completed without error now with both
the default settings and with the examples selected to build.
Just an FYI, when I selected the documentation build in the
cmake-gui... I got a cmake err
Hi Curtis,
I'll have to try and reproduce on a Linux box on my side. But could you try
to pull current master and check if you can get further ?
--
nǝıɥʇɐƜ
On 12 October 2016 at 17:57, Curtis Rubel wrote:
> Hi Mathieu,
>
>
> Basically that is exactly what I did and am getting an error.
>
> CMa
Hi Mathieu,
Basically that is exactly what I did and am getting an error.
CMake Error: File
/usr/local/3rdparty/osgQt-git/packaging/ld.so.conf.d/openscenegraph.conf.in
does not exist.
CMake Error at CMakeLists.txt:971 (CONFIGURE_FILE):
configure_file Problem configuring file
The ld.so.conf.
Hi Curtis,
The repository now lies next to osg's :
https://github.com/openscenegraph/osgQt
To be able to compile osgQt you need to have an existing osg installation
beforehand.
I'll try to make change the Readme to explain in better detail.
What I did (macOS with Qt5) :
git clone ...
cd osgQt
mkdi
Hi,
Just curious how things are proceeding with this process.
I saw Roberts request to test the latest 3.5.6 Master branch with the
new vertex buffer changes and would like to try and do that
but our entire baseline relies heavily on osgQt being present
to build against.
We are mainly a Linux
Hi Robert,
I received and confirmed your invitation on the OpenSceneGraph osgQt repo.
Thanks !
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Hi Mathieu,
On 11 October 2016 at 15:56, Mathieu MARACHE wrote:
> Hi Robert the project is ready since it is only a extraction of osgQt in
> terms of functionality. I've merged into master and tagged as 3.5.5
I have now forked your osgQt on openscenegraph:
https://github.com/openscenegraph/
Hi Robert the project is ready since it is only a extraction of osgQt in
terms of functionality. I've merged into master and tagged as 3.5.5
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-use
Hi Mathieu,
How are things progressing on the osgQt front? Is the project ready
to be moved to an openscenegraph/osgQt github repo?
Let me know when you are ready and I can fork your repo as
openscenegraph/osgQt and generate the appropriate write access for
you.
Robert.
It is a sensible but not very flexible way to answer the issue imho. I
could propose the "conan" way like we do internally (upload versioned
binary packages to a public repo). But I will make a proposal first.
___
osg-users mailing list
osg-users@lists.op
Hi Mathieu,
> If I want to compile osgQt using travisCI or appveyor I need to pull also
> osg's code to compile it ?
>
Maybe we could upload the OSG succesful builds in travis CI to docker. And
then pull it from osgQt build. I will need to figure out how to do this but
it cuold be an option.
Ch
Hi Mathieu,
Mathieu wrote:
> Qt4 is now on extended support (commercial) since december 2015. Which means
> that any project seriously using Qt should have migrated long ago (wink to my
> colleagues) !
>
I would not say "long ago" in general. We moved recently to Qt5. There are
several aspect
Hi Robert,
On Mon, Sep 19, 2016 at 9:46 AM Robert Osfield
wrote:
> Hi Mathieu,
>
> One of the items that could complicate things is the qfont plugin as this
> would normally be placed in the lib/osgPlugins-version directory. This
> coupling to a specific OSG version is not helpful for the osgQt
Hi Mathieu,
One of the items that could complicate things is the qfont plugin as this
would normally be placed in the lib/osgPlugins-version directory. This
coupling to a specific OSG version is not helpful for the osgQt build or
maintainers.
I think the solution is to simply place the
src/osgPl
HI Mathieu,
On 18 September 2016 at 01:49, Mathieu MARACHE
wrote:
> I cloned tom's attempt to reduce history :
> https://github.com/blobfish/osgQtCleaned01
>
> I'm now in the process of simplifying a bit some things, finding OT, OSG,
> etc.
I've just had a quick look at your osgQt repository, it
Hi again,
I've moved forward and compiled and executed osgQt on Qt5 on macOS.
The modifications are made on my repo (forked from Tom's) in a branch :
https://github.com/mathieu/osgQt/tree/findingOSG
There are still some bits like soversion that are hardcoded (the stock
FindOpenSceneGraph.cmake d
Hi Robert,
I cloned tom's attempt to reduce history : https://github.com/blobfish/
osgQtCleaned01
I'm now in the process of simplifying a bit some things, finding OT, OSG,
etc.
Something is still bothering me as OpenSceneGraph is not the only piece of
software osgQt depends on, but also OpenThre
On 16 September 2016 at 16:17, Mathieu MARACHE
wrote:
> Better approach ! Looks like we have a winner :-)
Do you want me to apply the script to my osgQt, or do you want to
apply them to your own.
Once we feel that osgQt is ready to be used standalone I'd suggest
forking which ever of our osgQt r
Better approach ! Looks like we have a winner :-)
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
Hi,
Here is my attempt to help. Here is a command that I have put together that
seems to be accomplishing the task. from 14240 commits to 1204.
Code:
git filter-branch \
--prune-empty \
--index-filter '
git ls-tree -z -r --name-only --full-tree $GIT_COMMIT \
| grep -z -v
Hi Mathieu,
Thanks for taking this further. I wonder if there is some easy way of
pruning down the repository as it seems crazy to be carrying the lots
of baggage around for what should be a small little project and
repository.
I guess the crude way would be to just copy the files across to a ne
Hi All,
I've gone through the process of striping the osgQt repository from osg
only related files in it's history. This means rewriting commits and
removing unnecessary files from each commit. This is a long process.
I've added a commit removing non osgQt related examples.
I then listed all the
Mathieu wrote:
>
> Anyone out there wanting to chip in ?
>
I can help - my time is very limited though. At the very least I can feedback
on the documentation, setup and use.
I have past experience with Qt/OSG/Delta3D and am currently reviving all that
knowledge on a personal project which c
Hi All,
I have done an initial experiment with cloning the OpenSceneGraph
repository and cutting it down to contain just the osgQt, qfont plugin
and the Qt related examples. I haven't got it compiling yet. I
posted it on my personal github account:
https://github.com/robertosfield/osgQt
It
Hi,
Regarding the hosting, within the openscenegraph account would be the best
I recon. Both for visibility and ease to find.
Concerning rights, you can setup "Collaborators" that will have push access
to the repository in the repository settings. You could then mandate a
maintainer the right to pu
HI Mathieu,
Thanks for offering to help out.
I agree the easiest way to create an osgQt project would be to clone
the whole OSG then cut down and then replace the CMake build to be a
bit more streamlined. I have written other NodeKits that have have
relatively straight forward CMake build.
I co
HI Sebastian,
To be clear, it's not a case of a democratic vote of whether osgQt
remains part of the core or not. I've discussed the mater at length
previously, it became clear that the current status quo isn't viable,
osgQt really should never have been merged in the first place, Qt is
such a hu
Hi,
I'd vote for keeping osgQT in the core, with maintenance for the
current Qt version only.
Basically that would mean to keep the legacy qt things out of the core,
thus reducing maintenance efforts but keeping compatibility for the
current versions.
Right now the Qt+OSG combination is frust
Hi Werner,
The key problem we have is that the osgQt can't support both Qt4 and
Qt5 without rebuilding osgQt. This is fine if you build the OSG
yourself, but for distributions that include OSG binaries have to
choose between OSG with Qt4 or Qt5. This just doesn't work for all
end users, it's bro
Hi All,
I use osgQt. Currently I'm on Qt 5.5 with OSG 3.4 but if I remember correctly
older OSG versions are not compatible with Qt5 and vice versa. So probably
there should be two different forks: osgQt4 from the OSG version compatible
with Qt4, and osgQt5 from an OSG version compatible with Qt
Hi Robert,
We are users of the osgQt library, we are in the process of migrating from
Qt4 to Qt5. I can propose to be the maintainer of the osgQt Nodekit...
I would propose, in order to keep the history, to fork the current osg repo
and cut out everything else to create an osg Nodekit library.
A
Hi Robert,
if I recognized well, there are still frequent questions on the list
about Qt-interface in OSG.
At least we are using it very intensely. There was not much move in the
interface since long and so
we just take it as it was and as it works so far.
The threading problem is a bit unsatisfac
Do we not have any Qt users anymore? No one care enough to chip in?
I'm not going to wait around forever before making decisions. I need
to get on with moving the OSG towards OSG-3.6.
The OSG/Qt users need to decide how they want to progress from here
once osgQt has been move out from the core O
Hi All,
The issue of supporting Qt4 and Qt5 isn't something we can do
concurrently with the current version of the OSG's osgQt library - the
compiler or the binaries distributor has to make a compile time
decision between Qt4 or Qt5.
We've discussed this topic before back then I resolved to remov
42 matches
Mail list logo
