Re: [rust-dev] 0.8 release
On 27.09.2013 15:09, Renato Lenzi wrote: Strange thing... after installing rust 08 on W7 System rustc.exe (or rust.exe or rusti.exe) doesn't start and Windows complains: the application was unable to start correctly (0xc005). The worst thing is that reinstalling rust07 i get the same error.. now i'm without Rust :-( ideas? Most likely it's because you still have the 0.7 dlls. Check in C:\Program Files (x86)\Rust\bin\rustc\i686-pc-mingw32\bin and C:\Program Files (x86)\Rust\bin\ and remove all files ending in -0.7.dll. Hopefully that fixes it. The way to avoid this is to uninstall the previous version before installing a new one I think, but I always forget. It'd be nice if the installer would clean up older libs. Cheers -- Jordi Boggiano @seldaek - http://nelm.io/jordi ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
[rust-dev] Fwd: 0.8 release
I've to try i usually install on my D hard drive in dirs named rust05, rust06, rust07... and, until today, this way has worked fine. but with rust08 i was unsuccessful A fresh install on a Windows 8 station gives error as well, complaining for some missing DLL... not a good situation for me thx a lot. On 27.09.2013 15:09, Renato Lenzi wrote: Strange thing... after installing rust 08 on W7 System rustc.exe (or rust.exe or rusti.exe) doesn't start and Windows complains: the application was unable to start correctly (0xc005). The worst thing is that reinstalling rust07 i get the same error.. now i'm without Rust :-( ideas? Most likely it's because you still have the 0.7 dlls. Check in C:\Program Files (x86)\Rust\bin\rustc\i686-pc-mingw32\bin and C:\Program Files (x86)\Rust\bin\ and remove all files ending in -0.7.dll. Hopefully that fixes it. The way to avoid this is to uninstall the previous version before installing a new one I think, but I always forget. It'd be nice if the installer would clean up older libs. Cheers -- Jordi Boggiano @seldaek - http://nelm.io/jordi ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] 0.8 release
You have mingw installed with required packages installed? Sent from my Windows Phone From: Renato Lenzimailto:rex...@gmail.com Sent: 9/27/2013 7:09 To: Rust-dev@mozilla.orgmailto:Rust-dev@mozilla.org Subject: [rust-dev] 0.8 release Strange thing... after installing rust 08 on W7 System rustc.exe (or rust.exe or rusti.exe) doesn't start and Windows complains: the application was unable to start correctly (0xc005). The worst thing is that reinstalling rust07 i get the same error.. now i'm without Rust :-( ideas? Regards. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] 0.8 release
Known issue: #5878 https://github.com/mozilla/rust/issues/5878. At mingw prompt, run: mingw-get upgrade g++4.6 mingw-get upgrade libpthread=2.8.0-3 This will roll some components back to older version that Rust binaries require. You can then copy libgcc_s_dw2-1.dll, libstdc++-6.dll and libpthread-2.dll from %mingw%\bin into Rust installation directory and run mingw-get upgrade to go back to latest versions. Vadim On Fri, Sep 27, 2013 at 6:09 AM, Renato Lenzi rex...@gmail.com wrote: Strange thing... after installing rust 08 on W7 System rustc.exe (or rust.exe or rusti.exe) doesn't start and Windows complains: the application was unable to start correctly (0xc005). The worst thing is that reinstalling rust07 i get the same error.. now i'm without Rust :-( ideas? Regards. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
[rust-dev] Fwd: 0.8 release
Oh yes this works fine. Thank you. ... Known issue: #5878 https://github.com/mozilla/rust/issues/5878. At mingw prompt, run: mingw-get upgrade g++4.6 mingw-get upgrade libpthread=2.8.0-3 This will roll some components back to older version that Rust binaries require. You can then copy libgcc_s_dw2-1.dll, libstdc++-6.dll and libpthread-2.dll from %mingw%\bin into Rust installation directory and run mingw-get upgrade to go back to latest versions. Vadim On Fri, Sep 27, 2013 at 6:09 AM, Renato Lenzi rex...@gmail.com wrote: Strange thing... after installing rust 08 on W7 System rustc.exe (or rust.exe or rusti.exe) doesn't start and Windows complains: the application was unable to start correctly (0xc005). The worst thing is that reinstalling rust07 i get the same error.. now i'm without Rust :-( ideas? Regards. ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
[rust-dev] OpenGL: gl-rs updated with command line generation options
gl-rs[1] is an OpenGL function loader for Rust. It exposes the full OpenGL API, loading the function pointers at runtime to ensure portability between systems with different graphics drivers. This capability is extremely important for developers who wish to make full use of state-of-the-art graphics hardware. The recent changes by Corey Richardson allow for the specification of what is generated by the loader. This means you don't have to generate the entire spec, like you used to (which resulted in a 1.6mb file) ./generator --version 3.3 --profile core ./generator --version 2.1 --extension GL_ARB_robustness --extension GL_EXT_draw_instanced We have included a 4.3 core profile loader so that you can get up to speed quickly without having to spend time generating the loader yourself. Hopefully with future updates to rustpkg you will be able to supply the generation options at the `extern mod` line in your source code. If you have any issues, questions or suggestions, you can contact me on irc.mozilla.org #rust-gamedev[2]. My handle is 'bjz'. Hopefully this helps to give Rust an extra boost in the realm of high-performance graphics! Regards, Brendan Zabarauskas [1]: https://github.com/bjz/gl-rs [2]: http://chat.mibbit.com/?server=irc.mozilla.orgchannel=%23rust-gamedev ___ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
[rust-dev] Crate-scoped non-trait implementations
Given the proposed privacy resolution rules (
https://github.com/mozilla/rust/issues/8215#issuecomment-24762188 )
there exists a concept of crate-scope for items: these can be used
within the implementation of the crate, but are inaccessible from other
crates. This is easy to do by introducing a private module:
mod private
{
pub fn crate_scoped_fn();
pub trait CrateScopedTrait;
pub struct CrateScopedStruct;
}
It's not clear to me whether or not this is possible (or whether it
should be) for non-trait implementations. Right now, if I do this:
pub struct S;
mod private
{
impl super::S
{
pub fn new() - super::S { super::S }
pub fn crate_local_api(self) - {}
}
}
I find that the associated function can't be used at all within a crate
or cross crate (issue #9584), while the method resolves in both cases,
but does not link cross-crate. What should happen in this case? I'd
prefer for the function and method to resolve within a crate, but not
cross crate.
Notably, this is not how trait implementations work today, as those are
resolved by looking at the location/privacy of the trait and not the
implementation. I think crate-scoped methods and associated functions
are very useful though, and it's worthwhile to have a different rule
for them.
Or maybe there should be an explicit keyword for the crate scope and
not bother with these bizarre privacy rules. Or maybe I am missing an
alternate way to accomplish this?
-SL
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
Re: [rust-dev] Introducing wxRust
As a Mac developer, you should have Xcode 5.0 installed, which comes with Clang
5.0 (based on LLVM 3.3svn), which is roughly equivalent to open-source Clang
3.3.
-Kevin
On Sep 27, 2013, at 8:51 PM, KENZ gelsoft kenz.gels...@gmail.com wrote:
I tried rust-bindgen finally, and it worked excellently. Great work!!
Since it requires Clang 3.3 which doesn't exist on OS X 10.8 setup,
I tried commit 3d49d7bcc0cf63b43a16a6cf52480fa9b752 and some tweak.
And some arguments are needed, for my project:
$ ./bindgen -x c++ ../wxRust/wxHaskell/wxc/src/include/wxc.h
`wx-config --cflags` --include stdint.h --include time.h
../wxRust/generated.rs
bindgen is C mode as default like clang or gcc are, so I understand it
requires `-x c++` option,
but I don't know why I have to explicitly include stdint.h and time.h
for size_t and uint8_t.
Do you have another recommended options?
My codegen.py just handles functions, so handling for other
definitions benefits.
So I want adopt rust-bindgen to generate extern fn part of my binding
for long-term plan.
Despite I know its Clang requirement changed for bitwidth support, but
as a Mac developer, I don't want to install the Clang 3.3 only for
rust-bindgen,
especially I don't want add a new prerequisite to my library.
Are there a posibility of optional Clang 3.1 support (without bitwidth
support)?
2013/9/26 Martin DeMello martindeme...@gmail.com:
no, but it might be feasible to add. not sure if it'd fall within the
scope of bindgen or not, but at least bindgen could emit some sort of
serialised data structure that would make generating the next level
binding easier.
martin
On Wed, Sep 25, 2013 at 4:49 PM, KENZ gelsoft kenz.gels...@gmail.com wrote:
Oh, I didn't know that project, thank you for information. I'll try it.
BTW, I chose to make own parser and generator to generate not only extern fn
decls but also next-level wrapper such as:
trait Frame {
pub fn show(self) {
unsafe {
wxFrame_Show(self.handle());
}
}
}
or so, would bindgen helps this use case? (c.f. parsed data accessible or
so.)
Did you try using bindgen on the wxc header file? If there were bits
it couldn't handle, I'd be interested in helping fix that.
martin
On Wed, Sep 25, 2013 at 10:49 AM, KENZ gelsoft kenz.gels...@gmail.com
wrote:
Hello, everyone.
I would like to introduce my experimental project, wxRust.
Which is a wxWidgets binding for Rust.
https://github.com/kenz-gelsoft/wxRust
This binding is based on the wxHaskell especially its wxc*1
C-Language wxWidgets binding part.
Currently, it just converts wxc's header file to `extern fn`s and
export them as a rust library.
Test program has just started working which opens a wxFrame
by calling wxc's C interface from extern fn.
Current state is pre-alpha experimental state, there's no stable API,
hard to use, but announced here for someone planning similar project.
I'm planning for next generating simple OOP style wrapper as rust
traits for each classes from wxc's header.
There is many problems to tackle, for example how it can work
with multitask or, library users can write wx GUI programs easier.
Any helps or feedbacks are welcome.
*1: [http://www.haskell.org/haskellwiki/WxHaskell#Status]
Thanks,
--
KENZ kenz.gels...@gmail.com
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
___
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
