Thiago, thank you very much for these explanations. About that option, it only
works on Windows so it's no good either way.
About generating wrappers for inlines, if you know of a tool that can do that -
as I mentioned earlier - it would be of great help to me.
On Tuesday, April 29, 2014 10:33
Em ter 29 abr 2014, às 08:06:37, Thiago Macieira escreveu:
> Em ter 29 abr 2014, às 04:45:37, Dimitar Dobrev escreveu:
> > Allan, I'm not talking about a custom build at all. This whole discussion
> > I
> > started is about how to avoid one. The results you see I've obtained from
> > the Qt 5.2.1 M
Em ter 29 abr 2014 08:08:35 você escreveu:
> Thiago,
>
> Thanks for that piece. I am not that familiar with such details of C++ so
> could you please explain why the function is public but compiled with
> hidden symbols?
[with permission to reply to the list]
There are two things here at stake:
I actually use https://github.com/mono/CppSharp . It has a parser and so on but
what I was asking for is a tool for generating wrappers. What I've been doing
so far is: get each inlined function -> get where it's invoked -> include the
header of the latter in a source file -> compile that with
Em ter 29 abr 2014, às 09:10:39, Dimitar Dobrev escreveu:
> Sharing with other bindings - now that's a great idea! I hadn't actually
> thought of the fact that such a wrapper is the same for any binding. If
> that could become a Qt module as you suggest, and presented as a binary
> download at qt-p
I'm not sure I understand your idea about compiling alongside. The binding is
C# so I'd have to either use C++/CLI or translate the body of the inline to C#
and compile that. The former works only for Windows, the latter is too much
work - essentially a C++ to C# converter. What is your suggesti
On Monday 28 April 2014 05:37:40 Dimitar Dobrev wrote:
> My problem (and, I'd say, any binding developer's) is
> that I can't tell users "my binding is great, you just need to compile Qt
> yourselves because the binary downloads don't work well enough" - nobody's
> going to use it.
But whoever is
I understand. Thank you all for your time. Kai, I think you can close the issue
as "Won't Fix".
Regards,
Dimitar Dobrev
On Tuesday, April 29, 2014 6:24 PM, Thiago Macieira
wrote:
Em ter 29 abr 2014, às 04:45:37, Dimitar Dobrev escreveu:
> Allan, I'm not talking about a custom build at all.
Em ter 29 abr 2014, às 04:45:37, Dimitar Dobrev escreveu:
> Allan, I'm not talking about a custom build at all. This whole discussion I
> started is about how to avoid one. The results you see I've obtained from
> the Qt 5.2.1 MinGW binaries as downloaded from qt-project.org.
There won't be a chan
Em ter 29 abr 2014, às 13:43:00, Allan Sandfeld Jensen escreveu:
> On Tuesday 29 April 2014, Dimitar Dobrev wrote:
> > They are not emitted. I've opened QtCore with
> > http://www.dependencywalker.com/ and the only symbols I can see for
> > QModelIndex are:
> >
> > _ZNK11QModelIndex4dataEi
> > _ZN
Em ter 29 abr 2014, às 01:30:24, Dimitar Dobrev escreveu:
> I don't need invisible inlines either but some of them - such as
> QModelIndex::row() - are visible. Is there any way to emit just the visible
> inlines?
Still hidden:
$ readelf -Ws --dyn-syms libQt5Core.so.5 | c++filt| grep QModelIn
Allan, I'm not talking about a custom build at all. This whole discussion I
started is about how to avoid one. The results you see I've obtained from the
Qt 5.2.1 MinGW binaries as downloaded from qt-project.org.
On Tuesday, April 29, 2014 2:43 PM, Allan Sandfeld Jensen
wrote:
On Tuesday 29
On Tuesday 29 April 2014, Dimitar Dobrev wrote:
> They are not emitted. I've opened QtCore with
> http://www.dependencywalker.com/ and the only symbols I can see for
> QModelIndex are:
>
> _ZNK11QModelIndex4dataEi
> _ZNK11QModelIndex5childEii
> _ZNK11QModelIndex5flagsEv
> _ZNK11QModelIndex6parentE
They are not emitted. I've opened QtCore with http://www.dependencywalker.com/
and the only symbols I can see for QModelIndex are:
_ZNK11QModelIndex4dataEi
_ZNK11QModelIndex5childEii
_ZNK11QModelIndex5flagsEv
_ZNK11QModelIndex6parentEv
_ZNK11QModelIndex7isValidEv
_ZNK11QModelIndex7siblingEii
_ZNK
On Tuesday 29 April 2014, Dimitar Dobrev wrote:
> I don't need invisible inlines either but some of them - such as
> QModelIndex::row() - are visible. Is there any way to emit just the
> visible inlines?
>
Shouldn't be needed they are emitted by default. Only static inlines are
omitted from t
Simon,
In the description of the issue in JIRA I've pointed out why I don't like the
solution with an additional C/C++ wrapper. In short, I would have to compile
and pack such a lib for each OS, and then my users would have to deploy that
different per OS lib.
I'm not sure I understand your an
On Tuesday 29. April 2014 01.30.24 Dimitar Dobrev wrote:
> I don't need invisible inlines either but some of them - such as
> QModelIndex::row() - are visible. Is there any way to emit just the visible
> inlines?
I think the pinvoke approach of creating bindings just won't work reliably
with
reveu:
> > -Original Message-
> > From: development-bounces+kai.koehne=digia@qt-project.org
> > Subject: [Development] Qt binaries with inlined functions
> >
> > Hello all,
> >
> > I'd like to start a discussion about .https://bugreport
Em seg 28 abr 2014, às 11:15:23, Koehne Kai escreveu:
> > -Original Message-
> > From: development-bounces+kai.koehne=digia@qt-project.org
> > Subject: [Development] Qt binaries with inlined functions
> >
> > Hello all,
> >
> > I
I think it depends on whether you see bindings as a single case or as multiple
cases (one per binding). About other, let's say, types of projects - I am not
aware.
About an option - do you mean an option in the, say, online installer? If it's
a compile option, I'm afraid you might as well not b
> -Original Message-
> From: Olivier Goffart [mailto:oliv...@woboq.com]
> [...]
> Maybe it should go in qt_module.prf
Thanks, that takes me one step further - linking Qt5Gui fails next. Anyhow,
Qt5Core succeeded:
Size of libQt5Core.so.5.3.0 without patch:5.9M
Size of libQt5Core.so.5.3.0
On Monday 28 April 2014 11:15:23 Koehne Kai wrote:
> > -Original Message-
> > From: development-bounces+kai.koehne=digia@qt-project.org
> > Subject: [Development] Qt binaries with inlined functions
> >
> > Hello all,
> >
> > I
Unfortunately, I don't. Perhaps you need to add the flag to QMAKE_CFLAGS as
well?
Dimitar
On Monday, April 28, 2014 2:15 PM, Koehne Kai wrote:
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> Subject: [Development] Qt binarie
> -Original Message-
> From: development-bounces+kai.koehne=digia@qt-project.org
> Subject: [Development] Qt binaries with inlined functions
>
>
>
> Hello all,
>
> I'd like to start a discussion about .https://bugreports.qt-
> project.o
itar Dobrev
Emne: [Development] Qt binaries with inlined functions
Hello all,
I'd like to start a discussion about
.https://bugreports.qt-project.org/browse/QTBUG-32995.Please share your
thoughts.
Regards,
Dimitar Dobrev___
D
Sendt: 10:44 lørdag 26. april 2014
Til: development@qt-project.org
Svar til: Dimitar Dobrev
Emne: [Development] Qt binaries with inlined functions
Hello all,
I'd like to start a discussion about
.https://bugreports.qt-project.org/browse/QTBUG-32995. Please share your
thoughts.
Hello all,
I'd like to start a discussion about
.https://bugreports.qt-project.org/browse/QTBUG-32995.Please share your
thoughts.
Regards,
Dimitar Dobrev___
Development mailing list
Development@qt-project.org
http://lists.qt-proj
27 matches
Mail list logo
