wxcode-users — Submission, Questions, Information

Re: [wxCode-users] Compiling wxvidcap

[Frank F. <ff...@us...>]

At 3-5-2007 15:31, John Labenski wrote:
>> Is it portable to linux also?if it is portable,which driver is used?
> 
> No, there is code for V4L2, but it is not nearly complete. It kinda'
> works for one particular usb camera I have, but for any other camera
> conversion routines must be written to convert from their format to
> 32bit RGB for wxImages. I do not plan to spend any time on it in the
> near future.

For Dorgem3 (that completely relies on wxVidCap) I have an alpha version 
for Win32 that does some basic jobs. I will try to compile it on my 
Ubuntu Linux and see how far I come with wxVidCap and my Q-Tec camera. 
Linux is quite new to me, so it will take some time to get it compiled. 
And I use the wxImage functions so there still is work to be done.

Regards,
Frank

Re: [wxCode-users] Compiling wxvidcap

[John L. <jla...@gm...>]

On 5/3/07, Ramachandran M <ra...@ta...> wrote:
>
> I downloaded .dsp and .dsw from the cvs source .Now i am able to compile it.

Good.

> Is it portable to linux also?if it is portable,which driver is used?

No, there is code for V4L2, but it is not nearly complete. It kinda'
works for one particular usb camera I have, but for any other camera
conversion routines must be written to convert from their format to
32bit RGB for wxImages. I do not plan to spend any time on it in the
near future.

Regards,
    John Labenski

Re: [wxCode-users] Compiling wxvidcap

[Ramachandran M <ra...@ta...>]

Thanks

I downloaded .dsp and .dsw from the cvs source .Now
i am able to compile it.

Is it portable to linux also?if it is portable,which
driver is used?

Ram

---- Original message ----

  Date: Wed, 02 May 2007 17:17:27 +0200
  From: Frank Fesevur <ff...@us...>
  Subject: Re: [wxCode-users] Compiling wxvidcap
  To: wxc...@li...

  >At 2-5-2007 8:40, Ramachandran M wrote:
  >> I have downloaded the wxcode.zip file.I want to
  compile wxvidcap
  >> component.But it has only .dsp file.
  >> How to compile a wxvidcap in wxmsw2.6.4 ?
  >> Is there any procedure to compile the wxcode
  componenets in wxmsw?
  >
  >The .dsp is a sub-file for a MSVC6 project
  (similar to a .vcproj file).
  >You can add it to a project.
  >
  >With MSVC it should compile out of the box. With
  gcc (both MinGW and
  >cygwin) it does not work, because of problems
  with the header vfw.h that
  >comes with these gcc versions. Haven't tried any
  other compiler or OS yet.
  >
  >Regards,
  >Frank
  >
  >
  >-------------------------------------------------------------------------
  >This SF.net email is sponsored by DB2 Express
  >Download DB2 Express C - the FREE version of DB2
  express and take
  >control of your XML. No limits. Just data. Click
  to get it now.
  >http://sourceforge.net/powerbar/db2/
  >_______________________________________________
  >wxCode-users mailing list
  >wxC...@li...
  >https://lists.sourceforge.net/lists/listinfo/wxcode-users

Re: [wxCode-users] Compiling wxvidcap

[Frank F. <ff...@us...>]

At 2-5-2007 8:40, Ramachandran M wrote:
> I have downloaded the wxcode.zip file.I want to compile wxvidcap 
> component.But it has only .dsp file.
> How to compile a wxvidcap in wxmsw2.6.4 ?
> Is there any procedure to compile the wxcode componenets in wxmsw?

The .dsp is a sub-file for a MSVC6 project (similar to a .vcproj file). 
You can add it to a project.

With MSVC it should compile out of the box. With gcc (both MinGW and 
cygwin) it does not work, because of problems with the header vfw.h that 
comes with these gcc versions. Haven't tried any other compiler or OS yet.

Regards,
Frank

Re: [wxCode-users] Compiling wxvidcap

[John L. <jla...@gm...>]

On 5/2/07, Ramachandran M <ra...@ta...> wrote:
>
> Hi
> I have downloaded the wxcode.zip file.I want to compile wxvidcap
> component.But it has only .dsp file.
> How to compile a wxvidcap in wxmsw2.6.4 ?
> Is there any procedure to compile the wxcode componenets in wxmsw?

What compiler do you want to use?

Regards,
    John Labenski

[wxCode-users] Compiling wxvidcap

[Ramachandran M <ra...@ta...>]

Hi
I have downloaded the wxcode.zip file.I want to
compile wxvidcap component.But it has only .dsp
file.
How to compile a wxvidcap in wxmsw2.6.4 ?
Is there any procedure to compile the wxcode
componenets in wxmsw?
Thanks
Ram

[wxCode-users] [ wxcode-Bugs-1705354 ] [wxSQLite3] Closing of database returns error

[SourceForge.net <no...@so...>]

Bugs item #1705354, was opened at 2007-04-22 21:02
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1705354&group_id=51305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Steven Van Ingelgem (g00fy)
Assigned to: Nobody/Anonymous (nobody)
Summary: [wxSQLite3] Closing of database returns error

Initial Comment:
When you have some prepared statements 'open', you need to close them before closing the database.

What could be argued in this case is that they should be closed along with the database (that way they will throw an error when accessed).


Greetz

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462816&aid=1705354&group_id=51305

[wxCode-users] [ wxcode-Feature Requests-1705323 ] [wxSQLite3] binding & retrieving id-sequences are confusing

[SourceForge.net <no...@so...>]

Feature Requests item #1705323, was opened at 2007-04-22 19:26
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462819&aid=1705323&group_id=51305

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Steven Van Ingelgem (g00fy)
Assigned to: Nobody/Anonymous (nobody)
Summary: [wxSQLite3] binding & retrieving id-sequences are confusing

Initial Comment:
When binding you use a sequence like 1, 2, 3, ... But when you want to retrieve something, the sequence is 0, 1, 2, ...

I think it's because of how SQLite works, but maybe it's better to change this behaviour that you both bind and retrieve starting from the same starting point (for example 0, like everything in C).
Otherwise it just gets confusing ;)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=462819&aid=1705323&group_id=51305

Re: [wxCode-users] wxcode specific bakefile problem

[Cursor <cu...@fr...>]

Hi.

It is wonderfull.
I like when all is done automatically.

Thanks very much.

Emilien

Le mercredi 11 avril 2007 à 21:35 +0200, Francesco Montorsi a écrit :
> Hi,
> 
> Cursor ha scritto:
> > Hi All.
> > 
> > In order to follow the wxcode guidelines for wxAvahi, I'm rewriting my
> > bakefiles with the wxcode bakefile system. To do that, I follow the page
> > http://wxcode.sourceforge.net/bakefile.php.
> I've just seen now that that page needs to be updated. Done now.
> 
> > My bakefile is pretty
> > identical to other component bakefiles.
> > 
> > In the step 5 : the bakefile_gen is not OK : 
> > [1/2] generating gnu from wxavahi.bkl
> > error: failed to set variable '__objtmp' to value
> > '$(sources2objects(value, id, OBJEXT))': duplicate target name 'gcc
> > $(WX_PORT)$(_BUILDDIR_SHARED_SUFFIX)$(DIRSEP)wxavahi_lib_resolve.o'
> >     at /usr/share/bakefile/rules/makefile.bkl:267
> >     when in <set> at /usr/share/bakefile/rules/makefile.bkl:267
> >     when in <sources>
> > at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:27
> >     when in <lib>
> > at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:26
> >     when processing target 'wxavahi_lib'
> > at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:26
> > [bakefile_gen] error: bakefile exited with error
> > 
> > The lib target is :
> >     <lib id="wxavahi_lib" template="wxcode-lib,avahicommon"
> > cond="WX_SHARED=='0'">
> >         <sources>$(fileList('src/*.cpp'))</sources>
> >         <headers>$(fileList('include/wx/avahi/*.h'))</headers>
> >     </lib>
> > 
> > I dont know why it duplicates target name.
> > The problem persists when I change lib's id.
> that's because you don't need to explicitely put those <sources> and 
> <headers> tags. wxCode presets already do that internally. So that 
> bakefile "sees" a list of sources in form:
> 
>   a.cpp b.cpp ... a.cpp b.cpp ...
> 
> and complains about duplicated source file name
> 
> Francesco
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> wxCode-users mailing list
> wxC...@li...
> https://lists.sourceforge.net/lists/listinfo/wxcode-users
> 

Re: [wxCode-users] wxcode specific bakefile problem

[Francesco M. <f18...@ya...>]

Hi,

Cursor ha scritto:
> Hi All.
> 
> In order to follow the wxcode guidelines for wxAvahi, I'm rewriting my
> bakefiles with the wxcode bakefile system. To do that, I follow the page
> http://wxcode.sourceforge.net/bakefile.php.
I've just seen now that that page needs to be updated. Done now.

> My bakefile is pretty
> identical to other component bakefiles.
> 
> In the step 5 : the bakefile_gen is not OK : 
> [1/2] generating gnu from wxavahi.bkl
> error: failed to set variable '__objtmp' to value
> '$(sources2objects(value, id, OBJEXT))': duplicate target name 'gcc
> $(WX_PORT)$(_BUILDDIR_SHARED_SUFFIX)$(DIRSEP)wxavahi_lib_resolve.o'
>     at /usr/share/bakefile/rules/makefile.bkl:267
>     when in <set> at /usr/share/bakefile/rules/makefile.bkl:267
>     when in <sources>
> at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:27
>     when in <lib>
> at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:26
>     when processing target 'wxavahi_lib'
> at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:26
> [bakefile_gen] error: bakefile exited with error
> 
> The lib target is :
>     <lib id="wxavahi_lib" template="wxcode-lib,avahicommon"
> cond="WX_SHARED=='0'">
>         <sources>$(fileList('src/*.cpp'))</sources>
>         <headers>$(fileList('include/wx/avahi/*.h'))</headers>
>     </lib>
> 
> I dont know why it duplicates target name.
> The problem persists when I change lib's id.
that's because you don't need to explicitely put those <sources> and 
<headers> tags. wxCode presets already do that internally. So that 
bakefile "sees" a list of sources in form:

  a.cpp b.cpp ... a.cpp b.cpp ...

and complains about duplicated source file name

Francesco

[wxCode-users] wxcode specific bakefile problem

[Cursor <cu...@fr...>]

Hi All.

In order to follow the wxcode guidelines for wxAvahi, I'm rewriting my
bakefiles with the wxcode bakefile system. To do that, I follow the page
http://wxcode.sourceforge.net/bakefile.php . My bakefile is pretty
identical to other component bakefiles.

In the step 5 : the bakefile_gen is not OK : 
[1/2] generating gnu from wxavahi.bkl
error: failed to set variable '__objtmp' to value
'$(sources2objects(value, id, OBJEXT))': duplicate target name 'gcc
$(WX_PORT)$(_BUILDDIR_SHARED_SUFFIX)$(DIRSEP)wxavahi_lib_resolve.o'
    at /usr/share/bakefile/rules/makefile.bkl:267
    when in <set> at /usr/share/bakefile/rules/makefile.bkl:267
    when in <sources>
at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:27
    when in <lib>
at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:26
    when processing target 'wxavahi_lib'
at /home/mimile/workspace/wxCode/components/avahi/build/wxavahi.bkl:26
[bakefile_gen] error: bakefile exited with error

The lib target is :
    <lib id="wxavahi_lib" template="wxcode-lib,avahicommon"
cond="WX_SHARED=='0'">
        <sources>$(fileList('src/*.cpp'))</sources>
        <headers>$(fileList('include/wx/avahi/*.h'))</headers>
    </lib>

I dont know why it duplicates target name.
The problem persists when I change lib's id.

The file is on the svn (wxCode/components/avahi/build/wxavahi.bkl)

Regards
Emilien

Re: [wxCode-users] wxCtb maintainance

[Francesco M. <f18...@ya...>]

Hi
,
jbu...@if... ha scritto:
> Hello Francesco,
> 
>> To complete the movement of the component you'd just need to remove the
>> CVS sources... I can do it for you if you say it's ok (i.e. you've
>> already moved all source files and don't need the CVS repo anymore).
> 
> ok, you can remove it. The svn sources are the newest one.
done

>> Last, I see wxCtb has a bakefile build system which is not however based
>> on wxCode bakefiles... that's fine but I wonder how it can adapt to the
>> many possible wxWidgets different configurations... using wxCode
>> bakefiles probably would result in a smaller bakefile and a better build
>> system :)
> 
> Yes, because the ctb library is used in some embedded systems and other pc 
 > applications without any wxWidget installation.
It's possible to make a bakefile which builds a lib without anything 
wx-related and then add a target (e.g. a sample) which builds against 
that lib and wxWidgets...

BTW I didn't know CTB could build also without wx given that its classes 
are named with the 'wx' prefix (AFAIR).

> I want to make the bakefile 
 >as simple as possible and my first trials with the wxCode based bakefiles
 >(one or more years ago) let me run in some trouble, I couldn't solve.
probably they do not exist anymore :)

 >Also I want to build the library independently from some needed 
directory structs
 >(maybe it's possible, but I couldn't figure out it), so the user can 
build the
 >libs without a wxWidget or wxCode installation.
that's possible too. You could just create an option USE_WXWIDGETS which 
would enable/disable the wx-specific portions.

> If you can give me some hints for a better, wxCode conform bakefile, that also 
 >create makefiles also for people without a wxWidget or wxCode 
installation,
 >that would be great :-)
wxCode stuff is not required at all by wxCode components build system. 
However wxWidgets stuff is.


>> Also I'm currently getting this:
>>
>> g++ -c -o release/wxctb_lib_timer.o -DNDEBUG  -D_THREAD_SAFE -pthread
>> -O0 -I../include   -MTrelease/wxctb_lib_timer.o -MF`echo
>> release/wxctb_lib_timer.o | sed -e 's,\.o$,.d,'` -MD ../src/linux/timer.cpp
>> ../src/linux/timer.cpp: In function ‘void kill_all_timer()’:
>> ../src/linux/timer.cpp:93: error: ‘pthread_kill_other_threads_np’ was
>> not declared in this scope
>>
>> and that's strange because adding a #include <pthread.h> does not solve
>> it...
> 
> That function is obsolete. Comment it out and try again. I will do that as soon as possible in the svn.
thanks, it now compiles.

However I see it does not uses wxWidgets even in the sample... so that 
in effect it does not uses wxWidgets at all. So, the question is: why 
call the classes 'wx*' and why make wxCTB a wxWidgets "component" ?

:)

Francesco

[wxCode-users] new FAQ item: How to submit patches to wxCode

[Francesco M. <f18...@ya...>]

Hi all,
    I've updated the FAQ page of wxCode with a new FAQ: How to submit 
modification back to the wxCode maintainer.

I think this is very useful to have as many people so far asked me 
details about patching. Now I can reply them just this link:

http://wxcode.sourceforge.net/faq.php#3

HTH,
Francesco

Re: [wxCode-users] wxstedit in shared + RTTI error

[klaas.holwerda <ng...@kl...>]

Francesco Montorsi wrote:
> very strange. This may need investigation: could it be because of some
> incorrect RTTI usage?
>   
I am not using wxProcess anywhere i know of.
>
> which seems to mean that it tells to ld to use static libs to resolve 
> _all_ symbols.
>   
Yes, so what? -Bstatic and -Bdynamic are used both, so its a mix 
generated by Cmake, if it finds a dynamic version , it will use that, 
else the static flag. Maybe this mix does not combine well, although i 
think even wxWidgets always links some libraries shared always.

Sofar i seem to be unable to set a flag to only use static or dynamic 
libsa to link to :-(

Klaas

Re: [wxCode-users] wxCtb maintainance

[<jbu...@if...>]

Hello Francesco,

> To complete the movement of the component you'd just need to remove the
> CVS sources... I can do it for you if you say it's ok (i.e. you've
> already moved all source files and don't need the CVS repo anymore).

ok, you can remove it. The svn sources are the newest one.

> Last, I see wxCtb has a bakefile build system which is not however based
> on wxCode bakefiles... that's fine but I wonder how it can adapt to the
> many possible wxWidgets different configurations... using wxCode
> bakefiles probably would result in a smaller bakefile and a better build
> system :)

Yes, because the ctb library is used in some embedded systems and other pc =
applications without any wxWidget installation. I want to make the bakefile=
 as simple as possible and my first trials with the wxCode based bakefiles =
(one or more years ago) let me run in some trouble, I couldn't solve. Also =
I want to build the library independently from some needed directory struct=
s (maybe it's possible, but I couldn't figure out it), so the user can buil=
d the libs without a wxWidget or wxCode installation.
If you can give me some hints for a better, wxCode conform bakefile, that a=
lso create makefiles also for people without a wxWidget or wxCode installat=
ion, that would be great :-)
=20
>
> Also I'm currently getting this:
>
> g++ -c -o release/wxctb_lib_timer.o -DNDEBUG  -D_THREAD_SAFE -pthread
> -O0 -I../include   -MTrelease/wxctb_lib_timer.o -MF`echo
> release/wxctb_lib_timer.o | sed -e 's,\.o$,.d,'` -MD ../src/linux/timer.c=
pp
> ../src/linux/timer.cpp: In function =E2=80=98void kill_all_timer()=E2=80=
=99:
> ../src/linux/timer.cpp:93: error: =E2=80=98pthread_kill_other_threads_np=
=E2=80=99 was
> not declared in this scope
>
> and that's strange because adding a #include <pthread.h> does not solve
> it...

That function is obsolete. Comment it out and try again. I will do that as =
soon as possible in the svn.

> > Can you also create a svn folder for my awx project, maybe
> > https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/componen=
ts
> >/awx I've add some improvments and would like to put these also in the s=
vn
> > repository.

Ok, need some days and let you know, when i'm ready.

> Sure, done.

again many thanks ;-)

> As for wxctb, once you've moved sources, please remove them from CVS.

You can remove it (but I don't want to waste your time ;-)

>
> thanks,
> Francesco

Many thanks for your effort and best regards
Joachim

Re: [wxCode-users] wxCtb maintainance

[Francesco M. <f18...@ya...>]

Hi,

jbu...@if... ha scritto:
> Hello Francesco,
> 
> Sorry for the delay, but I'm very busy with my main job these days and 
> couldn't find more time for my open source stuff ;-(
> I also had some problems with my email provider and the delivering of my last responses are refused. So sorry again.
sure, no problem. I know what you mean - I'm going to have a very busy 
period in 2 next weeks.

> I have checked in the ctb sources in the svn repository, you have told me: 
> https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/ctb
thanks!

To complete the movement of the component you'd just need to remove the 
CVS sources... I can do it for you if you say it's ok (i.e. you've 
already moved all source files and don't need the CVS repo anymore).

Last, I see wxCtb has a bakefile build system which is not however based 
on wxCode bakefiles... that's fine but I wonder how it can adapt to the 
many possible wxWidgets different configurations... using wxCode 
bakefiles probably would result in a smaller bakefile and a better build 
system :)

Also I'm currently getting this:

g++ -c -o release/wxctb_lib_timer.o -DNDEBUG  -D_THREAD_SAFE -pthread 
-O0 -I../include   -MTrelease/wxctb_lib_timer.o -MF`echo 
release/wxctb_lib_timer.o | sed -e 's,\.o$,.d,'` -MD ../src/linux/timer.cpp
../src/linux/timer.cpp: In function ‘void kill_all_timer()’:
../src/linux/timer.cpp:93: error: ‘pthread_kill_other_threads_np’ was 
not declared in this scope

and that's strange because adding a #include <pthread.h> does not solve 
it...


> Can you also create a svn folder for my awx project, maybe
> https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/awx
> I've add some improvments and would like to put these also in the svn repository.
Sure, done.

As for wxctb, once you've moved sources, please remove them from CVS.

thanks,
Francesco

Re: [wxCode-users] wxCtb maintainance

[<jbu...@if...>]

Hello Francesco,

Sorry for the delay, but I'm very busy with my main job these days and 
couldn't find more time for my open source stuff ;-(
I also had some problems with my email provider and the delivering of my last responses are refused. So sorry again.

I have checked in the ctb sources in the svn repository, you have told me: 
https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/ctb

Can you also create a svn folder for my awx project, maybe
https://wxcode.svn.sourceforge.net/svnroot/wxcode/trunk/wxCode/components/awx
I've add some improvments and would like to put these also in the svn repository.
 
This would be great :-)

Best regards and many thanks for your friendly help.
Joachim

[wxCode-users] Email test

[<jbu...@if...>]

This is a test. Please ignore it.

[wxCode-users] <warnings>max</warnings> in wxCode bakefiles

[Francesco M. <f18...@ya...>]

Hi all,
     I've just noticed that since the last big change in wxCode 
bakefiles, warnings were not being set anymore to "max". It's usually a 
good idea to put it to "max" in order to be able to spot all possible 
sources of run-time errors in compile stage.

Thus I've added this flag to all wxCode templates (to be precise to a 
template from which all other wxCode templates derive): this means that 
next time you regen you'll have max warnings set. If you don't like this 
you can always add a:

    <warnings>default</warnings>

tag to your target to restore the 'normal' level of warnings.

Francesco

Re: [wxCode-users] wxstedit in shared + RTTI error

[Francesco M. <f18...@ya...>]

klaas.holwerda ha scritto:
> Hi,
> 
> After days of searching i finally discovered the reason behind the error 
> this:
> 
> [klaas@dhcppc2 editmdi]$ ./sample_editor_editmdi
> 17:57:41: Debug: ./src/common/object.cpp(244): assert 
> "sm_classTable->Get(m_className) == NULL" failed in Register(): Class 
> "wxProcess" already in RTTI table - have you used 
> IMPLEMENT_DYNAMIC_CLASS() multiple times or linked some object file twice)?
very strange. This may need investigation: could it be because of some 
incorrect RTTI usage?

> E.g. In the following linking line changing -Wl,-Bdynamic 
> -lwxcode_gtk2d_stedit-2.8 into -Wl,-Bstatic -lwxcode_gtk2d_stedit-2.8
> Makes it work fine. (order/place of the wxstedit lib does not matter, 
> also linking wxLua static or  shared  makes no difference.
> It comes back to wxstedit  linking shared.
I'm not sure to understand... but as you say this is probably related to 
cmake's default behaviour of putting -Wl,-Bdynamic flag in the linker line:

 From ld docs:

        -Bstatic
        -dn
        -non_shared
        -static
            Do not link against shared libraries.  This is only 
meaningful on platforms for  which
            shared libraries are supported.  The different variants of 
this option are for compat‐
            ibility with various systems.  You may use this option 
multiple times on  the  command
            line:  it  affects library searching for -l options which 
follow it.  This option also
            implies --unresolved-symbols=report-all.  This option can be 
used with -shared.  Doing
            so means that a shared library is being created but that all 
of the library’s external
            references must be resolved by pulling in entries from 
static libraries.

which seems to mean that it tells to ld to use static libs to resolve 
_all_ symbols.

Francesco

[wxCode-users] wxstedit in shared + RTTI error

[klaas.holwerda <ng...@kl...>]

Hi,

After days of searching i finally discovered the reason behind the error 
this:

[klaas@dhcppc2 editmdi]$ ./sample_editor_editmdi
17:57:41: Debug: ./src/common/object.cpp(244): assert 
"sm_classTable->Get(m_className) == NULL" failed in Register(): Class 
"wxProcess" already in RTTI table - have you used 
IMPLEMENT_DYNAMIC_CLASS() multiple times or linked some object file twice)?
./src/common/object.cpp(244): assert "sm_classTable->Get(m_className) == 
NULL" failed in Register(): Class "wxProcess" already in RTTI table - 
have you used IMPLEMENT_DYNAMIC_CLASS() multiple times or linked some 
object file twice)?
Trace/breakpoint trap

As you see it complains about wxProcess RTTI, but WHY??

So i discovered that to make it go away is linking wxstedit in as static 
and not shared.
E.g. In the following linking line changing -Wl,-Bdynamic 
-lwxcode_gtk2d_stedit-2.8 into -Wl,-Bstatic -lwxcode_gtk2d_stedit-2.8
Makes it work fine. (order/place of the wxstedit lib does not matter, 
also linking wxLua static or  shared  makes no difference.
It comes back to wxstedit  linking shared.
I can not tell why this is, but i think i better let it know here, since 
it was hard to find.
To bad cmake chooses shared libraries in favor  of static libs,  so i 
don't have a solution yet.

regards,

Klaas

[klaas@dhcppc2 editmdi]$  /usr/bin/c++      -fPIC 
"CMakeFiles/sample_editor_editmdi.dir/editmdi.o"   -o 
sample_editor_editmdi -rdynamic -L/home/klaas/wxwin/buildart/lib 
-L/home/klaas/wxwin/wxLua/lib -L/usr/local/lib 
-L/home/klaas/wxwin/wxCode/components/wxstedit/lib 
-L/home/klaas/wxwin/buildart/lib/ -Wl,-Bdynamic 
-lwxcode_gtk2d_stedit-2.8 -Wl,-Bstatic -lwxart2d_gtk2d_aggdrawer-2.8 
-lwxart2d_gtk2d_curves-2.8 -lwxart2d_gtk2d_editor-2.8 
-lwxart2d_gtk2d_canextobj-2.8 -lwxart2d_gtk2d_canvas-2.8 
-lwxart2d_gtk2d_artbase-2.8 -lwxart2d_gtk2d_docview-2.8 
-lwxart2d_gtk2d_svgio-2.8 -lwxart2d_gtk2d_gdsio-2.8 
-lwxart2d_gtk2d_keyio-2.8 -lwxart2d_gtk2d_xmlparse-2.8 
-lwxart2d_gtk2d_general-2.8 -lwxart2d_gtk2d_luawraps-2.8 -lkbool 
-Wl,-Bdynamic -lwxlua_gtk2d_wxluadebug-2.8 -lwxlua_gtk2d_wxluasocket-2.8 
-lwxlua_gtk2d_wxlua-2.8 -lwxlua_gtk2d_wxbind-2.8 
-lwxlua_gtk2d_wxbindstc-2.8 -llua5.1 -Wl,-Bdynamic -lexpat -Wl,-Bstatic 
-lantigrain -Wl,-Bdynamic `/usr/bin/freetype-config --libs` 
-L/usr/local/lib -pthread -Wl,-Bstatic -lwx_gtk2d_stc-2.8 
-lwx_gtk2d_qa-2.8 -lwx_gtk2d_xrc-2.8 -lwx_gtk2d_html-2.8 
-lwx_gtk2d_adv-2.8 -lwx_based_xml-2.8 -lwx_based_net-2.8 
-lwx_gtk2d_core-2.8 -lwx_based-2.8 -Wl,-Bdynamic -lexpat -L/lib 
-lgtk-x11-2.0 -lgdk-x11-2.0 -latk-1.0 -lgdk_pixbuf-2.0 -lpango-1.0 
-lgobject-2.0 -lgmodule-2.0 -lgthread-2.0 -lglib-2.0 -lXinerama 
-lXxf86vm -lSM -lpng -ljpeg -ltiff -lz -ldl -lm  -Wl,-Bdynamic 
-lfreetype 
-Wl,-rpath,/home/klaas/wxwin/buildart/lib:/home/klaas/wxwin/wxLua/lib:/usr/local/lib:/home/klaas/wxwin/wxCode/components/wxstedit/lib:/home/klaas/wxwin/buildart/lib/ 

Re: [wxCode-users] wxstedit static build

[John L. <jla...@gm...>]

On 3/29/07, Francesco Montorsi <f18...@ya...> wrote:
> > ar @AROPTIONS@ lib/libwxcode_gtk2d_stedit-2.8.a stedit_lib_stedit.o
> the @AROPTIONS@ symbol should have been substituted by the "configure"
> process... btw I do see the same error with the from-CVS configure script.

This is good, I compiled wxstedit a while back in OSX and got a
similar error about an extra @ or something. I thought it was just a
quirk with OSX's gcc and didn't have time to look into it further.

> However if I regen the script locally, the problem disappear.

Why would that work for you and not me? Are the CVS files in
wxCode/build/autoconf different than in SVN?

I use Mandriva 2006 (but I don't think this is the problem):
autoconf2.1-2.13-25mdv2007.0
automake1.8-1.9.6-3mdk
automake1.7-1.7.9-3mdk
autoconf2.5-2.59-7mdv2007.0

> John, did you regenerated it or just manually change the 0.2.0 => 0.2.2
> version in the script?

Oops, I'm busted, I just manually changed it. I tried to regenerate it
using acregen.sh and cleaned out what I thought were all the cache
files, but no matter what I did I kept getting 0.2.0 in the generated
configure.

> BTW I've taken the freedom to commit my working version of "configure"...

Thank you.
     John Labenski

Re: [wxCode-users] wxstedit static build

[klaas.holwerda <ng...@kl...>]

Francesco Montorsi wrote:
> Hi,
>
>    note1: if you don't feel "make clean" is enough, you can use "make 
> distclean" to clean your build folder ;)
>
>    note2: autoconf allows out-of-tree builds. Do
>
>    mkdir mybuild
>    cd mybuild
>    ../configure
>    make
>
> to build out-of-tree wxstedit and/or other bakefile-based wxCode 
> components ;)
>   
Starting to like it ;-)
> ./configure 
> --with-wx-config="/usr/local/lib/wx/config/gtk2-ansi-debug-static-2.8"
>   
I see, makes sense.
Is there a place in wxWiki/wxCode  to mention/read  those know how  things?
> BTW I've taken the freedom to commit my working version of "configure"...
>   
Thanks!
Works again,

Klaas

Re: [wxCode-users] wxstedit static build

[Francesco M. <f18...@ya...>]

Hi,

   note1: if you don't feel "make clean" is enough, you can use "make 
distclean" to clean your build folder ;)

   note2: autoconf allows out-of-tree builds. Do

   mkdir mybuild
   cd mybuild
   ../configure
   make

to build out-of-tree wxstedit and/or other bakefile-based wxCode 
components ;)


klaas.holwerda ha scritto:
> Next i thought to try my other installed wxWidgest again, using this:
> 
> ./configure --with-wx-config=gtk2-ansi-debug-2.8
> 
> Oops one more error.
AFAIK (I admit I've never used it very often) the --with-wx-config 
option requires that you specify the path to the "wx-config" script to 
use, not the signature of the build you want to use.
E.g.

./configure 
--with-wx-config="/usr/local/lib/wx/config/gtk2-ansi-debug-static-2.8"



> ar @AROPTIONS@ lib/libwxcode_gtk2d_stedit-2.8.a stedit_lib_stedit.o 
the @AROPTIONS@ symbol should have been substituted by the "configure" 
process... btw I do see the same error with the from-CVS configure script.

However if I regen the script locally, the problem disappear.

John, did you regenerated it or just manually change the 0.2.0 => 0.2.2 
version in the script?

BTW I've taken the freedom to commit my working version of "configure"...

Francesco

[wxCode-users] wxstedit static build

[klaas.holwerda <ng...@kl...>]

Hi,

After compiling wxstedit in shared ( as by default wxWidgets ).
I now wanted to try static mode.
It looks like there is a problem, even after removing and checking out 
wxstedit again completely.
( see last dump down here, )

Next i thought to try my other installed wxWidgest again, using this:

./configure --with-wx-config=gtk2-ansi-debug-2.8

Oops one more error.

( the real problem i am after has to do with wxLua, as soon as i am 
linking wxArt2D with wxLua, i get the linking error:
for class wxProcess class definition registered twice. So i thought it 
might have to do with static/shared build.
But i first need to be able to static build again)

Klaas

$ ./configure --with-wx-config=gtk2-ansi-debug-2.8
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking target system type... i686-pc-linux-gnu
checking for the --enable-debug option... will be automatically detected
checking for the --enable-unicode option... will be automatically detected
checking for the --enable-shared option... will be automatically detected
checking for the --with-toolkit option... will be automatically detected
checking for the --with-wxshared option... will be automatically detected
checking for the --with-wxversion option... will be automatically detected
checking for gtk2-ansi-debug-2.8... no
./configure: line 2096: test: -lt: unary operator expected
./configure: line 2111: --selected_config: command not found
checking if wxWidgets was built with UNICODE enabled... no
checking if wxWidgets was built in DEBUG mode... no
checking if wxWidgets was built in STATIC mode... no
checking which wxWidgets toolkit was selected... configure: error:
Cannot detect the currently installed wxWidgets port !
Please check your 'wx-config --cxxflags'...

[klaas@dhcppc2 wxstedit]$

============================================================================
Result of configure:

----------------------------------------------------------------
Configuration for wxstedit 1.2.4 successfully completed.
Summary of main configuration settings for wxstedit:
- DEBUG build
- ANSI mode
- STATIC mode

The wxWidgets build which will be used by wxstedit 1.2.4
has the following settings:
- DEBUG build
- ANSI mode
- STATIC mode
- VERSION: 2.8.3
- PORT: gtk2

Now, just run make.
----------------------------------------------------------------

[klaas@dhcppc2 wxstedit]$ make
g++ -c -o stedit_lib_stedit.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stedit.cpp
./src/stedit.cpp: In member function ‘bool wxSTEditor::Create(wxWindow*, 
wxWindowID, const wxPoint&, const wxSize&, long int, const wxString&)’:
./src/stedit.cpp:213: warning: ‘SetBestSize’ is deprecated (declared at 
/usr/local/include/wx-2.8/wx/window.h:1414)
g++ -c -o stedit_lib_stedlgs.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stedlgs.cpp
g++ -c -o stedit_lib_stedlgs_wdr.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stedlgs_wdr.cpp
g++ -c -o stedit_lib_steexprt.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/steexprt.cpp
g++ -c -o stedit_lib_stefindr.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stefindr.cpp
g++ -c -o stedit_lib_steframe.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/steframe.cpp
g++ -c -o stedit_lib_stelangs.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stelangs.cpp
g++ -c -o stedit_lib_stemenum.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stemenum.cpp
g++ -c -o stedit_lib_stenoteb.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stenoteb.cpp
g++ -c -o stedit_lib_steopts.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/steopts.cpp
g++ -c -o stedit_lib_steprefs.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/steprefs.cpp
g++ -c -o stedit_lib_steprint.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/steprint.cpp
g++ -c -o stedit_lib_steshell.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/steshell.cpp
g++ -c -o stedit_lib_stesplit.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stesplit.cpp
g++ -c -o stedit_lib_stestyls.o -I./include -I/contrib/include 
-I/usr/local/lib/wx/include/gtk2-ansi-debug-static-2.8 
-I/usr/local/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES 
-D__WXDEBUG__ -D__WXGTK__ -pthread -g -O0 ./src/stestyls.cpp
rm -f lib/libwxcode_gtk2d_stedit-2.8.a
ar @AROPTIONS@ lib/libwxcode_gtk2d_stedit-2.8.a stedit_lib_stedit.o 
stedit_lib_stedlgs.o stedit_lib_stedlgs_wdr.o stedit_lib_steexprt.o 
stedit_lib_stefindr.o stedit_lib_steframe.o stedit_lib_stelangs.o 
stedit_lib_stemenum.o stedit_lib_stenoteb.o stedit_lib_steopts.o 
stedit_lib_steprefs.o stedit_lib_steprint.o stedit_lib_steshell.o 
stedit_lib_stesplit.o stedit_lib_stestyls.o
ar: illegal option -- @
Usage: ar [emulation options] [-]{dmpqrstx}[abcfilNoPsSuvV] 
[member-name] [count] archive-file file...
ar -M [<mri-script]
commands:
d - delete file(s) from the archive
m[ab] - move file(s) in the archive
p - print file(s) found in the archive
q[f] - quick append file(s) to the archive
r[ab][f][u] - replace existing or insert new file(s) into the archive
t - display contents of archive
x[o] - extract file(s) from the archive
command specific modifiers:
[a] - put file(s) after [member-name]
[b] - put file(s) before [member-name] (same as [i])
[N] - use instance [count] of name
[f] - truncate inserted file names
[P] - use full path names when matching
[o] - preserve original dates
[u] - only replace files that are newer than current archive contents
generic modifiers:
[c] - do not warn if the library had to be created
[s] - create an archive index (cf. ranlib)
[S] - do not build a symbol table
[v] - be verbose
[V] - display the version number
@<file> - read options from <file>
emulation options:
No emulation specific options
ar: supported targets: elf32-i386 a.out-i386-linux efi-app-ia32 
elf32-little elf32-big srec symbolsrec tekhex binary ihex trad-core
make: *** [lib/libwxcode_gtk2d_stedit-2.8.a] Error 1
[klaas@dhcppc2 wxstedit]$