headers
qt-bugs | 1 Dec 2002 03:50

RE: [Issue N11069] Questioin about qt cygwin port

Hi,

> Okay, I have looked where this MACRO is used and have added
> Q_OS_CYGWIN in such
> places, so I don't need Q_OS_LINUX.

Great!

> > Why use a separate Q_OS_CYGWIN_WIN32 macro? If the Win32 calls are
> > really needed I don't mind
>
> Performance reasons.
>
> > Are there really serious performance problems? Can't they be
> > considered
> > Cygwin problems that could be fixed in upcoming releases if they are
> > reported?
> >
> Yes, cygwin in general has performance problems with file io, which I
> have
> inspected some month ago, but was unable to fix. :-( It may be that
> there are
> some guys in the future, who are able to fix this, but in the
> meantime,
> especially for kde on cygwin, this patches are necessary to ensure a
> minimum
> performance.

I see.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Robert Collins | 1 Dec 2002 14:28

RE: [Issue N11069] Questioin about qt cygwin port

On Sun, 2002-12-01 at 13:50, qt-bugs <at> trolltech.com wrote:

> > Yes, cygwin in general has performance problems with file io, which I
> > have
> > inspected some month ago, but was unable to fix. :-( It may be that
> > there are
> > some guys in the future, who are able to fix this, but in the
> > meantime,
> > especially for kde on cygwin, this patches are necessary to ensure a
> > minimum
> > performance.
> 
> I see.
> 
> If I get the time to install Cygwin on a Windows machine some day, I'll
> maybe see whether Cygwin can be improved. We usually prefer to get
> errors fixed in 3rd party tools and libraries instead of adding tons of
> workarounds in Qt. Anyway... for now I don't have Cygwin installed.

Cygwin is a general purpose POSIX layer, and as in nearly any general
purpose solution, there are tradeoff's. We are always interested in
improving cygwin though :}.

Rob
Permalink | Reply | 0 comments |
headers
Ralf Habacker | 2 Dec 2002 08:11
Picon
Favicon

FW: [kde-cygwin - Help] kbuildsycoca problem

Hi Waldo,

In the last time users got this message. Any idea, whats going wrong ?
Ralf

> this seems to be installing fine with the debug procedure. . .until i run into
> problems with kded and kwin.
>  after the line in the debug procedure on debug page after kwin &
> where it should tell me I have exec_new notify from klauncher it instead says
> ERROR<KServiceFactory>unexpected object entry in KSycoca database
<type=2949197>
>  what's going on?
>
> ______________________________________________________________________
> You are receiving this email because you elected to monitor this forum.
> To stop monitoring this forum, login to SourceForge and visit:
> https://sourceforge.net/forum/monitor.php?forum_id=85789
>
Permalink | Reply | 501 comments |
headers
Ralf Habacker | 3 Dec 2002 08:07
Picon
Favicon

kmail using story for wanted

Hi all,

some time after the first release of the kdenetwork package I have heard from
people using kmail in their daily work.
Now I've got a request from someone of the kde core team for a story, which
would be published on dot.kde.org and/or KMails homepage. Is anyone here, who
can take this job, then please let me know.
It seems to me, that this would give us a positive reputation and probably also
some critical comments so someone is needed, who is able to follow the resulting
threads on the kde dot and give the right answer :-)

Ralf
Permalink | Reply | 0 comments |
headers
Waldo Bastian | 2 Dec 2002 13:21
Picon
Favicon

Re: FW: [kde-cygwin - Help] kbuildsycoca problem

On Monday 02 December 2002 08:11, Ralf Habacker wrote:
> Hi Waldo,
>
> In the last time users got this message. Any idea, whats going wrong ?
> Ralf
>
> > this seems to be installing fine with the debug procedure. . .until i run
> > into problems with kded and kwin.
> >  after the line in the debug procedure on debug page after kwin &
> > where it should tell me I have exec_new notify from klauncher it instead
> > says ERROR<KServiceFactory>unexpected object entry in KSycoca database
>
> <type=2949197>
>
> >  what's going on?

You managed to break ksycoca somehow :-] Each sycoca entry starts with a 
type-id that identifies the kind of object that follows. See the KST_ enum in 
ksycocatype.h

294919 is clearly not a valid type. Somehow you have corruption in your sycoca 
database.

Cheers,
Waldo
--

-- 
bastian <at> kde.org -=|[ SuSE, The Linux Desktop Experts ]|=- bastian <at> suse.com
Permalink | Reply | 501 comments |
headers
Bob Tanner | 3 Dec 2002 23:17
Favicon

Re: qt 3.1 port planing

On Tuesday 26 November 2002 06:24 pm, Ralf Habacker wrote:
> If you don't know how to, see below.
>
> $cd <your qt-3-snapshot>
> $cvs import -m "QT 3.1.0 rc2 Release" qt-3 QT_IMPORT qt_3_1_0_rc2
>

I these cvs commit (see post to list from cvs). I get the following error:

Connection to cvs.kde-cygwin.sourceforge.net closed by remote host.
cvs [import aborted]: end of file from server (consult above messages if any)

And there are several conflicts (as shown in the cvs commit email).
--

-- 
Bob Tanner <tanner <at> real-time.com>         | Phone : (952)943-8700
http://www.mn-linux.org, Minnesota, Linux | Fax   : (952)943-8500
http://www.linuxjustworks.com             | Linux Just Works!         
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288
Permalink | Reply | 1 comment |
headers
Bob Tanner | 4 Dec 2002 05:53
Favicon

Re: qt 3.1 port planing

On Tuesday 26 November 2002 06:24 pm, Ralf Habacker wrote:
> If you don't know how to, see below.
>
> $cd <your qt-3-snapshot>
> $cvs import -m "QT 3.1.0 rc2 Release" qt-3 QT_IMPORT qt_3_1_0_rc2

Most of the conflicts are with the $Id$ tags in the files again. Why is this 
happening? More importantly, why don't I get these issues with the other open 
source projects I contribute to?

--

-- 
Bob Tanner <tanner <at> real-time.com>         | Phone : (952)943-8700
http://www.mn-linux.org, Minnesota, Linux | Fax   : (952)943-8500
http://www.linuxjustworks.com             | Linux Just Works!         
Key fingerprint = AB15 0BDF BCDE 4369 5B42  1973 7CF1 A709 2CC1 B288
Permalink | Reply | 1 comment |
headers
Ralf Habacker | 4 Dec 2002 07:57
Picon
Favicon

RE: qt 3.1 port planing

> On Tuesday 26 November 2002 06:24 pm, Ralf Habacker wrote:
> > If you don't know how to, see below.
> >
> > $cd <your qt-3-snapshot>
> > $cvs import -m "QT 3.1.0 rc2 Release" qt-3 QT_IMPORT qt_3_1_0_rc2
>
> Most of the conflicts are with the $Id$ tags in the files again. Why is this
> happening? More importantly, why don't I get these issues with the other open
> source projects I contribute to?
>
See http://www.cvshome.org/docs/manual/cvs_13.html#SEC105

"13.5 How to handle keyword substitution with cvs import

The sources which you are importing may contain keywords (see section 12.
Keyword substitution). For example, the vendor may use CVS or some other system
which uses similar keyword expansion syntax. If you just import the files in the
default fashion, then the keyword expansions supplied by the vendor will be
replaced by keyword expansions supplied by your own copy of CVS. It may be more
convenient to maintain the expansions supplied by the vendor, so that this
information can supply information about the sources that you imported from the
vendor.

To maintain the keyword expansions supplied by the vendor, supply the `-ko'
option to cvs import the first time you import the file.
This will turn off keyword expansion for that file entirely, so if you want to
be more selective you'll have to think about what you want and use the `-k'
option to cvs update or cvs admin as appropriate.
"
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bob Tanner | 4 Dec 2002 09:17
Favicon

Re: qt 3.1 port planing

On Tuesday 26 November 2002 06:24 pm, Ralf Habacker wrote:
> $cd <your qt-3-snapshot>
> $cvs import -m "QT 3.1.0 rc2 Release" qt-3 QT_IMPORT qt_3_1_0_rc2
>
> $ cerate a diff file
> $ cd <your checked out qt-3 dir>
> $ cvs diff -ubB -r qt_3_1_0_rc1 -r qt_3_1_0_rc2  | tee qt310_rc1_rc2.dif
> $ patch -p0 <qt310_rc1_rc2.dif
> $ cvs ci -m "update to qt3.1.0 rc2"

Got everything patched, but something broke in the merge. Example explains it 
best:

g++ -c -o pbuilder_pbx.o -g -I. -Igenerators -Igenerators/unix 
-Igenerators/win32  -Igenerators/mac -I <at> OUT_QTDIR <at> /include 
-I <at> REL_QTDIR <at> /include -I <at> OUT_QTDIR <at> /src/tools -DQT_NO_TEXTCODEC 
-DQT_NO_COMPONENT -DQT_NO_STL -I/cygdrive/r/BUILD/qt-3/mkspecs/cygwin-g++ 
generators/mac/pbuilder_pbx.cpp

 <at> OUT_QTDIR <at> 
 <at> REL_QTDIR <at> 
 <at> OUT_QTDIR <at> 

Are not being replaced. This worked before the merge, so I must have missed 
something or messed something up.

--

-- 
Bob Tanner <tanner <at> real-time.com>         | Phone : (952)943-8700
http://www.mn-linux.org, Minnesota, Linux | Fax   : (952)943-8500
http://www.linuxjustworks.com             | Linux Just Works!
(Continue reading)

Permalink | Reply | 3 comments |
headers
Bob Tanner | 4 Dec 2002 09:31
Favicon

Re: qt 3.1 port planing

On Wednesday 04 December 2002 02:17 am, Bob Tanner wrote:
> On Tuesday 26 November 2002 06:24 pm, Ralf Habacker wrote:
> > $cd <your qt-3-snapshot>
> > $cvs import -m "QT 3.1.0 rc2 Release" qt-3 QT_IMPORT qt_3_1_0_rc2
> >
> > $ cerate a diff file
> > $ cd <your checked out qt-3 dir>
> > $ cvs diff -ubB -r qt_3_1_0_rc1 -r qt_3_1_0_rc2  | tee qt310_rc1_rc2.dif
> > $ patch -p0 <qt310_rc1_rc2.dif
> > $ cvs ci -m "update to qt3.1.0 rc2"
>
> Got everything patched, but something broke in the merge. Example explains
> it best:
>
> g++ -c -o pbuilder_pbx.o -g -I. -Igenerators -Igenerators/unix
> -Igenerators/win32  -Igenerators/mac -I <at> OUT_QTDIR <at> /include
> -I <at> REL_QTDIR <at> /include -I <at> OUT_QTDIR <at> /src/tools -DQT_NO_TEXTCODEC
> -DQT_NO_COMPONENT -DQT_NO_STL -I/cygdrive/r/BUILD/qt-3/mkspecs/cygwin-g++
> generators/mac/pbuilder_pbx.cpp
>
>  <at> OUT_QTDIR <at> 
>  <at> REL_QTDIR <at> 
>  <at> OUT_QTDIR <at> 
>
> Are not being replaced. This worked before the merge, so I must have missed
> something or messed something up.

Found the problem, messed up merge of configure. I'll work on it tommorrow. 

--

--
(Continue reading)

Permalink | Reply | 0 comments |

Gmane