|
|
Post by egghead on Sept 29, 2017 4:10:01 GMT
Unfortunately, I have holidays until 2nd October and therefore no access to dev machine. I can send you the logs only on 3rd  |
|
|
|
Post by Alex Epifanov on Sept 29, 2017 4:13:04 GMT
egghead OK, no probs, we'll try to find out. What is your dev machine OS? WinXP 32bit?
|
|
|
|
Post by egghead on Sept 29, 2017 4:16:10 GMT
No, as stated earlier, Windows 7 64 bit. But I'm using Rhostudio 32 bit on it.
|
|
|
|
Post by georgy on Sept 29, 2017 16:04:21 GMT
|
|
|
|
Post by egghead on Sept 30, 2017 2:02:53 GMT
Thanks, georgy, will definitely try it out next week.
|
|
|
|
Post by egghead on Oct 3, 2017 6:10:34 GMT
Problem solved. What I did was to download and install the Visual C++ Redistributable for Visual Studio 2012 Update 4 (https://www.microsoft.com/en-us/download/details.aspx?id=30679)
|
|
|
|
Post by egghead on Oct 3, 2017 14:56:54 GMT
I should add though, that there's a significant delay for the start page to show up after the splash screen in Rhosim
|
|
|
|
Post by egghead on Oct 5, 2017 9:42:33 GMT
Yes we plan to update ruby version we ship in installer, but it should not conflict with framework... Well, updated ruby version is required in installer. When I try to build with a native extension in Android, its giving an error. Snippet : [INFO] Running dx utility cp -r d:/RhoMobileSuite6.0.0/ruby/lib/ruby/gems/1.9.1/gems/rhodes-6.0.0/platform /android/proguard D:/extensiontest/bin/tmp [INFO] Packaging Assets and Jars [INFO] Add assets/lib/_socket.iseq to D:/extensiontest/bin/rhodes.ap_... [INFO] Packaging Native Libs [INFO] Packaging java resources rake aborted! NameError: uninitialized constant File::FNM_EXTGLOB Apparently, FNM_EXTGLOB was introduced in Ruby 2.0 and not supported in 1.9.x and therefore trying to compile with 1.9.3 gives that error. There may be other consequences. I tried building the same project in Rhodes 5.1.1 and it compiled successfully. I thought I should let you guys know. |
|
|
|
Post by Alex Epifanov on Oct 6, 2017 13:43:31 GMT
egghead we compile with same ruby version we use inside mobile app (2.3.4) so it should not be the reason. The ruby version shipped in Windows installer is only needed to run rake scripts ( and you don't have to install it if you already have new version - you can just install gems to your ruby. ) Please share your files - source, configuration etc. We'll reproduce it on our side.
|
|
|
|
Post by egghead on Oct 6, 2017 15:13:30 GMT
Alex, I'm not sure I understand what you mean. No, I don't have Ruby 2.3.4 for build. If it was so, I expect it to build successfully. My Ruby version for build is coming from RMS, so 1.9.3 whereas the VM is 2.3.4. These 2 don't match. So solution is to upgrade the Ruby that comes with installer. Is that possible? If yes, when can we expect updated installer?
To reproduce, simply run installer in a Windows machine without any Ruby installed, create a simple extension, and compile. That error will show up.
I'm away from dev PC so cannot upload my source code, but I'm sure you can reproduce at your end with a clean install using installer.
|
|
|
|
Post by Alex Epifanov on Oct 6, 2017 15:54:05 GMT
Ruby compiled files, ISEQs, are made not with Ruby coming with RMS. We make it with separate RubyWin/RubyMac executable based on our own modified Ruby codebase, which is same as Ruby VM runing on device, currently 2.3.4.
|
|
|
|
Post by Alex Epifanov on Oct 6, 2017 15:56:34 GMT
We will try to reproduce your case
|
|
|
|
Post by egghead on Oct 6, 2017 16:11:39 GMT
Thanks, Alex.
Maybe I'm using the term "compile" wrongly. What I mean is
build : rake device:android:debug
from command line
|
|
|
|
Post by Alex Epifanov on Oct 6, 2017 16:16:22 GMT
Thanks, Alex. Maybe I'm using the term "compile" wrongly. What I mean is build : rake device:android:debug from command line Yes, it might be something more related to the build scripts. |
|
|
|
Post by egghead on Oct 9, 2017 4:18:12 GMT
The build output log is in mylog.txt attached in file mylog.txt (31.71 KB) |
|
