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
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
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
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
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
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
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!)
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
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
---
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
On 3/10/06, Francesco Montorsi [EMAIL PROTECTED] 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
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
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
---
This SF.Net email is sponsored by xPML, a
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
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
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:
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
Anders F Björklund ha scritto:
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
Francesco Montorsi wrote:
You might want to do the same thing for the include dir, too... ?
the headers should not cause any conflict since they go in
$PREFIX/include/lua/include
(note the double include string in path - required for wxLua moduling
system). IIRC correctly lua puts its
On 3/10/06, Anders F Björklund [EMAIL PROTECTED] wrote:
Francesco Montorsi wrote:
You might want to do the same thing for the include dir, too... ?
the headers should not cause any conflict since they go in
$PREFIX/include/lua/include
(note the double include string in path - required
Anders F Björklund ha scritto:
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
On 3/10/06, Anders F Björklund [EMAIL PROTECTED] wrote:
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
Francesco Montorsi:
I've tried to link statically also expat but in the final ELF ldd
still shows expat.so.1 is needed.
Probably because wxWidgets was not compiled using autopackage's gcc
wrapper, apgcc, which cuts down dependencies... I'm going to create an
autopackage for wxWidgets but
As mentioned earlier, all that needs to be
done to support RPM building is to put a
spec file into a build/rpm directory...
Here is such a file, that I just wrote:
http://www.algonet.se/~afb/wx/wxlua.spec
(builds with: rpmbuild -ba wxlua.spec)
Should be straight-forward to convert
Version: into
23 matches
Mail list logo
