wxlua-users — wxLua list for users and developers

Re: [Wxlua-users] 2.6.2.0 packaged but...

[<af...@al...>]

Francesco Montorsi wrote:

>    finally I've tagged the wxLua tree and created all binary and 
> source packages, updated download page and created a news entry.

Just for fun, I tried downloading the .package file and installing it.
(following the instructions linked to from the download package...)

The install went OK, it fetched the rest of autopackage OK and so on.
A little scared of binary installers,this was just for experimenting.


But when I ran the wxLuaEditor application from the menu, it just died.
Running it again, from the shell, showed that libexpat.so.1 not found ?

I only have libexpat.so.0 on my Linux machine, running Fedora Core 4.
libtiff.so.4 also seemed to be missing, when checking it with "ldd"...


Can this be fixed, by linking those two libraries statically or so ?
--anders

Re: [Wxlua-users] Re: Why does wxLua install lua too ?

[<af...@al...>]

Francesco Montorsi wrote:

> well, wxLua embeds lua so I thought it was natural to install it.

It should probably be installed under another name, though ?

Otherwise it *will* cause conflicts.

> The lua library installed won't create any conflict since it's named 
> something like:
> libwxlua_gtk2_lua-2.6.a
>
> maybe we should adopt a custom name also for the lua exec ?
> Maybe wxlua-lua ?

You might want to do the same thing for the include dir, too... ?

--anders

PS. Download all fixed now. (not empty anymore)

[Wxlua-users] Re: 2.6.2.0 packaged but...

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

Anders F Björklund ha scritto:
> John Labenski wrote:
> 
>>>  could someone give me rights shortly (after some hours uploaded
>>> files are removed if not binded) or bind the files with a wxLua release?
>>
>> Ok, all done.
> 
> I get an empty (0-byte) file, for wxlua-2.6.2.0.tar.gz ?
I'm still testing all packages but you're right: for some reason the 
upload was not successful.

I've uploaded it again.

Francesco

[Wxlua-users] Re: Why does wxLua install lua too ?

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

Anders F Björklund ha scritto:
> 
> Was a bit surprised, when my new Lua 5.1 was
> overwritten by the old Lua 5.0.2 from wxLua...
> 
> Is there any reason why it installs "lua" too ?
> (I only expected it to install the wxlua ones)
well, wxLua embeds lua so I thought it was natural to install it.
The lua library installed won't create any conflict since it's named 
something like:

libwxlua_gtk2_lua-2.6.a

maybe we should adopt a custom name also for the lua exec ?
Maybe wxlua-lua ?

Francesco

[Wxlua-users] Re: configure and CXXFLAGS

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

Anders F Björklund ha scritto:
> 
> How do I get configure to respect the CXXFLAGS ?
> 
> Seems that it just replaces them with "-g0 -O2" ?
> (and whatever wx-config --cxxflags add, of course)

arg, this seems to be a little problem which I never spotted. It should 
be fixed now...

Francesco

[Wxlua-users] Why does wxLua install lua too ?

[<af...@al...>]

Was a bit surprised, when my new Lua 5.1 was
overwritten by the old Lua 5.0.2 from wxLua...

Is there any reason why it installs "lua" too ?
(I only expected it to install the wxlua ones)

--anders

Re: [Wxlua-users] 2.6.2.0 packaged but...

[<af...@al...>]

John Labenski wrote:

>>  could someone give me rights shortly (after some hours uploaded
>> files are removed if not binded) or bind the files with a wxLua 
>> release?
>
> Ok, all done.

I get an empty (0-byte) file, for wxlua-2.6.2.0.tar.gz ?

--anders

Re: [Wxlua-users] 2.6.2.0 packaged but...

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

On 3/10/06, Francesco Montorsi <f18...@ya...> wrote:
> Hi,
>     finally I've tagged the wxLua tree and created all binary and source
> packages, updated download page and created a news entry.
>
> Unfortunately it seems I don't have file-release permissions on SF and
> thus even if I already uploaded the files to upload.sf.net I cannot bind
> them with a wxLua release...
>
>      could someone give me rights shortly (after some hours uploaded
> files are removed if not binded) or bind the files with a wxLua release?

Ok, all done.

Thanks again for everything,
    John Labenski

[Wxlua-users] configure and CXXFLAGS

[<af...@al...>]

How do I get configure to respect the CXXFLAGS ?

Seems that it just replaces them with "-g0 -O2" ?
(and whatever wx-config --cxxflags add, of course)

--anders

[Wxlua-users] 2.6.2.0 packaged but...

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

Hi,
    finally I've tagged the wxLua tree and created all binary and source 
packages, updated download page and created a news entry.

Unfortunately it seems I don't have file-release permissions on SF and 
thus even if I already uploaded the files to upload.sf.net I cannot bind 
them with a wxLua release...

     could someone give me rights shortly (after some hours uploaded 
files are removed if not binded) or bind the files with a wxLua release?

Thanks,
Francesco

Re: [Wxlua-users] Re: Release today?

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

On 3/10/06, Francesco Montorsi <f18...@ya...> wrote:
> I've done various compile tests on wxMSW, wxGTK.
> Everything should be working there.
>
> I'm now testing through SF compile farm the AMD64 builds (but first I
> need to get wx built there and it will take long...)
>
> Now I'll study some electronics (my university exams are coming closer
> and closer!) then at about GMT 18 I'll make the branch, the packages and
> upload everything on SF if I don't hear anything.
>
> John, we should also make the release of wxStEdit...

Ok, I'll try to see if I have some time to do it today. I'm going to
be pretty busy, out of town as well, for the next week.

-John Labenski

[Wxlua-users] Re: Release today?

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

I've done various compile tests on wxMSW, wxGTK.
Everything should be working there.

I'm now testing through SF compile farm the AMD64 builds (but first I 
need to get wx built there and it will take long...)

Now I'll study some electronics (my university exams are coming closer 
and closer!) then at about GMT 18 I'll make the branch, the packages and 
upload everything on SF if I don't hear anything.

John, we should also make the release of wxStEdit...

Francesco

[Wxlua-users] Re: Release today?

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

Francesco Montorsi ha scritto:
> k. holwerda ha scritto:
>> Hi Francesco,
>>
>> Last time i tested MSW all looked fine, that was a few days ago.
>> Next desaster struck my notebook with all mail etc., it overheated and 
>> broke down.
>> So i have bin bussy trying to get my data back from its harddisk :-(
> bad news... having had so many problems with PC, too, I'm now much more 
> quiet
...setting up an automatic backup scripts (written by me;)) which 
auto-backups my data on a regular basis in the shutdown process.
But these kind of things are easily scriptable only on Linux ;)

Francesco

Re: [Wxlua-users] Re: wxMac - packaging details

[<af...@al...>]

Francesco Montorsi wrote:

>> I don't actually think we'll even need an Installer PKG...
> this gives me some other conceptual problem: Installer PKG was not 
> mentioned in point 1) or 2)... I thought we were going to release a 
> .dmg...

Normally you wrap a PKG inside a DMG, if you need to
get permission or install in "invisible" directories
(the Finder hides /usr/local and the rest from the user)

For wxLua, we're not really going to distribute the
bin and lib and so on to the "end user", so we can
let users wanting those use source or DarwinPorts/Fink ?

Thus, we won't require PKG in this project. Right you are.

Making a DMG is pretty simple, just proprietary to Apple:
hdiutil create -srcfolder wxLua -fs HFS+ -format UDZO -ov wxLua.dmg
hdiutil internet-enable -yes -quiet wxLua.dmg

>> (better to do an RPM spec file in that case, and use RPM ?)
> RPM is evil as it is distro- and version-distro- specific.
> That's why I'm using autopackage for Linux binary package.
> So I'd prefer to avoid it...

huh ?
I was just talking about a .spec file, for building RPMS yourself ?
You don't even have to distribute SRPMS, as one can use the tarball.

Nothing evil about that, I like RPM.
Binary RPMS, however: Oh dear... :-)

--anders

[Wxlua-users] Re: wxMac - packaging details

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

Anders F Björklund ha scritto:
> Francesco Montorsi wrote:
> 
>> So, we just need to add to build\macbundle the Info.plist and maybe a 
>> simple script which calls the utilities to actually build the package, 
>> isn't it?
>>
>> I can then add Info.plist to configure list of files to create. It 
>> won't be used by Unix installations but only by Mac ones...
> 
> Something like that, yes...
> 
> Just that we'll need one such Info.plist for all three apps,
> or do a common template for all and generate the specifics ?
> (I guess the version numbers of them would follow wxLua's ?)
I would keep them separed as they look like short XML files.
And yes, the versioning will be the same.

> 
> For an example of what it looks like, you can view:
> http://www.algonet.se/~afb/wx/CodeBlocks.Info.plist
> It's missing the bindings to certain filetypes, though.
Seems not too complicated - let me know if you can send me these file 
within today so that they could be included in the source package.

> 
> Building the app can be a small shell script (or Makefile)
sure - just choose the one you prefer.

> I don't actually think we'll even need an Installer PKG...
this gives me some other conceptual problem: Installer PKG was not 
mentioned in point 1) or 2)... I thought we were going to release a .dmg...

> (better to do an RPM spec file in that case, and use RPM ?)
RPM is evil as it is distro- and version-distro- specific.
That's why I'm using autopackage for Linux binary package.
So I'd prefer to avoid it...

Francesco

Re: [Wxlua-users] Re: wxMac - packaging details

[<af...@al...>]

Francesco Montorsi wrote:

> So, we just need to add to build\macbundle the Info.plist and maybe a 
> simple script which calls the utilities to actually build the package, 
> isn't it?
>
> I can then add Info.plist to configure list of files to create. It 
> won't be used by Unix installations but only by Mac ones...

Something like that, yes...

Just that we'll need one such Info.plist for all three apps,
or do a common template for all and generate the specifics ?
(I guess the version numbers of them would follow wxLua's ?)

For an example of what it looks like, you can view:
http://www.algonet.se/~afb/wx/CodeBlocks.Info.plist
It's missing the bindings to certain filetypes, though.

Building the app can be a small shell script (or Makefile)
I don't actually think we'll even need an Installer PKG...
(better to do an RPM spec file in that case, and use RPM ?)

--anders

[Wxlua-users] Re: wxMac - packaging details

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

Anders F Björklund ha scritto:
> Here is how the Mac packaging works... (="will work")
> 
> Dual: just like Mac OS X itself, this can be done in
> two different ways, the "Mac way" or the "Unix way"
> (with the Mac way being more of the NeXT way really,
> but that is a topic for a whole other discussion...)
> 
> --------------------------------------------------
> 
> 1.
> For the Mac way, I will do static links like this:
> 
> wxLua.app/
>     Contents/
>         Info.plist
>         MacOS/
>             wxlua
>         Resources/
>             wxLua.icns
> wxLuaEditor.app/ (ditto)
> LuaCan.app/ (ditto)
> 
> The "Info.plist" can be generated from Info.plist.in,
> it's an XML file that describes the application...
> 
> This will not get "installed", but the user can drag
> it to /Applications or ~/Applications, or wherever.
> 
> This "wxLua.app" bundle is what we set as the
> application to launch for .lua files, and so on.
> 
> The Samples themselves will just go in a folder.
> Package will be either ZIP or DMG, probably dmg ?
> 
> ---------------------------------------------------------
> 
> 2.
> For the Unix way, it will be shared linked like:
> 
> $PREFIX/bin/wxlua ->
>         $PREFIX/lib/libwxlua_mac_wxlua-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxbindstc-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxbind-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxluasocket-2.6.0.dylib
>         $PREFIX/lib/libwxlua_mac_wxluadebug-2.6.0.dylib
>        $PREFIX/lib/libwx_mac-2.6.0.dylib
> 
> That last library is not provided by wxLua,
> it's the wxWidgets shared library being used.
> (could be either wxMac or wxGTK, and either
> monolithic or split into several - as usual)
> 
>        $PREFIX/lib/libwx_mac_stc-2.6.0.dylib
>        $PREFIX/lib/libstedit.0.dylib
> 
> Will probably link STC and wxStEdit statically ?
> (just to avoid problems in DarwinPorts and Fink)
> 
> On Mac OS X, "commandline" programs launch in the
> background and don't receive any events (sucks!),
> so we will fake this for the "Unix way" by adding
> an oldskool Mac resource fork, including the icon:
> 
> /Developer/Tools/Rez -d wxLua.r Carbon.r -o $PREFIX/bin/wxlua
> /Developer/Tools/SetFile -a C $PREFIX/bin/wxlua
> 
> This will make it look nice, and : receive events too. :)
> All these files will get installed, in the usual $PREFIX.
> 
> ---------------------------------------------------------
> 
> Hope that clears things up ? Mac OS X is a strange hybrid...
this helped indeed to understand Mac world ;)
So, we just need to add to build\macbundle the Info.plist and maybe a 
simple script which calls the utilities to actually build the package, 
isn't it?

I can then add Info.plist to configure list of files to create. It won't 
be used by Unix installations but only by Mac ones...

Francesco

Re: [Wxlua-users] Re: Release today?

[<af...@al...>]

Francesco Montorsi wrote:

>> And it doesn't need to be a Mac disk image / package yet, if you
>> release a tarball then the "Unix" repositories can pick it up ?
>> (that would be "DarwinPorts" and "Fink" projects, for Mac -
>> http://www.darwinports.org | http://fink.sourceforge.net/)
> I had heard of these projects but never looked into it... they looks  
> interesting. What exactly do we need to do to have this software  
> packaged there ?

Write a ports/spec file that installs it in the proper location, I  
guess...

Looks something like this:
http://www.darwinports.org/darwinports/dports/graphics/wxWidgets/ 
Portfile

Fink is like Debian, so they require for a maintainer to volunteer  
first.

--anders

[Wxlua-users] wxMac - packaging details

[<af...@al...>]

Here is how the Mac packaging works... (="will work")

Dual: just like Mac OS X itself, this can be done in
two different ways, the "Mac way" or the "Unix way"
(with the Mac way being more of the NeXT way really,
but that is a topic for a whole other discussion...)

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

1.
For the Mac way, I will do static links like this:

wxLua.app/
	Contents/
		Info.plist
		MacOS/
			wxlua
		Resources/
			wxLua.icns
wxLuaEditor.app/ (ditto)
LuaCan.app/ (ditto)

The "Info.plist" can be generated from Info.plist.in,
it's an XML file that describes the application...

This will not get "installed", but the user can drag
it to /Applications or ~/Applications, or wherever.

This "wxLua.app" bundle is what we set as the
application to launch for .lua files, and so on.

The Samples themselves will just go in a folder.
Package will be either ZIP or DMG, probably dmg ?

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

2.
For the Unix way, it will be shared linked like:

$PREFIX/bin/wxlua ->
         $PREFIX/lib/libwxlua_mac_wxlua-2.6.0.dylib
         $PREFIX/lib/libwxlua_mac_wxbindstc-2.6.0.dylib
         $PREFIX/lib/libwxlua_mac_wxbind-2.6.0.dylib
         $PREFIX/lib/libwxlua_mac_wxluasocket-2.6.0.dylib
         $PREFIX/lib/libwxlua_mac_wxluadebug-2.6.0.dylib
	   $PREFIX/lib/libwx_mac-2.6.0.dylib

That last library is not provided by wxLua,
it's the wxWidgets shared library being used.
(could be either wxMac or wxGTK, and either
monolithic or split into several - as usual)

        $PREFIX/lib/libwx_mac_stc-2.6.0.dylib
        $PREFIX/lib/libstedit.0.dylib

Will probably link STC and wxStEdit statically ?
(just to avoid problems in DarwinPorts and Fink)

On Mac OS X, "commandline" programs launch in the
background and don't receive any events (sucks!),
so we will fake this for the "Unix way" by adding
an oldskool Mac resource fork, including the icon:

/Developer/Tools/Rez -d wxLua.r Carbon.r -o $PREFIX/bin/wxlua
/Developer/Tools/SetFile -a C $PREFIX/bin/wxlua

This will make it look nice, and : receive events too. :)
All these files will get installed, in the usual $PREFIX.

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

Hope that clears things up ? Mac OS X is a strange hybrid...

--anders

[Wxlua-users] Re: Release today?

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

Anders F Björklund ha scritto:
> Francesco Montorsi wrote:
> 
>> Hi,
>>    if everyone agree, we could proceed today with release 2.6.2.0, as 
>> expected...
>>
>> Autopackage stuff and mac bundle could be not fully ready but they can 
>> be added later.
>>
>> If proceeding with release, I'll package wxLua this afternoon and then 
>> upload it to SF servers. Just let me know.
> 
> I think you should release it...
> 
> The wxMac stuff doesn't work fully yet, but if we release a package
> then more people can test it and provide bug reports ? And all win ?
yes, exactly. The idea is this.
For our first release we don't need to have it 100% fully working.

> 
> And it doesn't need to be a Mac disk image / package yet, if you
> release a tarball then the "Unix" repositories can pick it up ?
> (that would be "DarwinPorts" and "Fink" projects, for Mac -
> http://www.darwinports.org | http://fink.sourceforge.net/)
I had heard of these projects but never looked into it... they looks 
interesting. What exactly do we need to do to have this software 
packaged there ?

> 
> Please include the wxLua.r.gz file, though. It'll help those.
> (as it's the easiest way to get it going from a $PREFIX/bin)
done

Francesco

[Wxlua-users] Re: Release today?

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

k. holwerda ha scritto:
> Hi Francesco,
> 
> Last time i tested MSW all looked fine, that was a few days ago.
> Next desaster struck my notebook with all mail etc., it overheated and 
> broke down.
> So i have bin bussy trying to get my data back from its harddisk :-(
bad news... having had so many problems with PC, too, I'm now much more 
quiet


> 
> Anyway, i think it is still save to go ahead from the MSW point of view.
> I will test the release itself again next, and if something is not 
> right, we can always make a next release ;-)
right

> 
> How are we going to celebrate this big event? :-)
I think announcing the release at:
-> wxWidgets users list
-> lua users list

will be enough ;)

Francesco

> 
> Klaas
> 
> Francesco Montorsi wrote:
> 
>> Hi,
>>    if everyone agree, we could proceed today with release 2.6.2.0, as 
>> expected...
>>
>> Autopackage stuff and mac bundle could be not fully ready but they can 
>> be added later.
>>
>> If proceeding with release, I'll package wxLua this afternoon and then 
>> upload it to SF servers. Just let me know.
>>
>> Also, it's important to create a branch, maybe RELEASE_2_6_2_0.
>>
> 

Re: [Wxlua-users] Release today?

[<af...@al...>]

Francesco Montorsi wrote:

> Hi,
>    if everyone agree, we could proceed today with release 2.6.2.0, as 
> expected...
>
> Autopackage stuff and mac bundle could be not fully ready but they can 
> be added later.
>
> If proceeding with release, I'll package wxLua this afternoon and then 
> upload it to SF servers. Just let me know.

I think you should release it...

The wxMac stuff doesn't work fully yet, but if we release a package
then more people can test it and provide bug reports ? And all win ?

And it doesn't need to be a Mac disk image / package yet, if you
release a tarball then the "Unix" repositories can pick it up ?
(that would be "DarwinPorts" and "Fink" projects, for Mac -
http://www.darwinports.org | http://fink.sourceforge.net/)

Please include the wxLua.r.gz file, though. It'll help those.
(as it's the easiest way to get it going from a $PREFIX/bin)

--anders

Re: [Wxlua-users] Re: wxLua for wxMac

[<af...@al...>]

John Labenski wrote:

>> Will recompile wxLua with full debugging symbols enabled tomorrow, I
>> think.
>
> That would be great, sorry but I can't help without some more
> information. I can't imagine what could fail in
> wxLuaEditorApp::OnInit, but a line number would help!

Here you go then:

Program received signal EXC_BAD_ACCESS, Could not access memory.
0x0000809c in wxLuaEditorApp::OnInit() (this=0x13210c0) at 
../apps/wxluaedit/src/wxluaedit.cpp:195
195                 frame->GetEditor()->LoadFile( fileNames[0] );

I'll experiment more with it tonight.

--anders

Re: [Wxlua-users] Release today?

[k. h. <kla...@nl...>]

Hi Francesco,

Last time i tested MSW all looked fine, that was a few days ago.
Next desaster struck my notebook with all mail etc., it overheated and 
broke down.
So i have bin bussy trying to get my data back from its harddisk :-(

Anyway, i think it is still save to go ahead from the MSW point of view.
I will test the release itself again next, and if something is not 
right, we can always make a next release ;-)

How are we going to celebrate this big event? :-)

Klaas

Francesco Montorsi wrote:

> Hi,
>    if everyone agree, we could proceed today with release 2.6.2.0, as 
> expected...
>
> Autopackage stuff and mac bundle could be not fully ready but they can 
> be added later.
>
> If proceeding with release, I'll package wxLua this afternoon and then 
> upload it to SF servers. Just let me know.
>
> Also, it's important to create a branch, maybe RELEASE_2_6_2_0.
>

-- 
Unclassified

[Wxlua-users] Release today?

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

Hi,
    if everyone agree, we could proceed today with release 2.6.2.0, as 
expected...

Autopackage stuff and mac bundle could be not fully ready but they can 
be added later.

If proceeding with release, I'll package wxLua this afternoon and then 
upload it to SF servers. Just let me know.

Also, it's important to create a branch, maybe RELEASE_2_6_2_0.

Let me know,
Francesco