ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Rafael Luque
Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.
Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Uko2
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.

Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Rafael Luque
I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.


Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Uko2
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko


On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.



Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Rafael Luque
Thank you! I'm looking forward to hearing from you about the new version.

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko



On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.




Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Uko2
Hi Rafael,

now ViDI should work. I haven’t been working on it for a while, but feel free to report more issues, as I’ll get back to it soon.

Uko


On 24 Apr 2015, at 09:57, Rafael Luque <[hidden email]> wrote:

Thank you! I'm looking forward to hearing from you about the new version.

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko



On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.





Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Rafael Luque
Hi Uko

I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

This is the stack trace for your information:

===========================================

NBFFICallout>>loaderForArgNamed:
NBFFICallout>>loaderForArgNamed:indirectIndex:
NBFFICallout>>argName:indirectIndex:type:ptrArity:
NBFnSpecParser>>parseArgument
NBFnSpecParser>>parseArguments
NBFnSpecParser>>parseAnonFunction:
NBFFICallout>>anonSpec:
[ :t3 | 
t3
useEmitCall;
callType: conv;
sender: context;
parseOptions: options;
anonSpec: t1;
generate: t2 ] in NBFFICalloutAPI>>function:emit:
[ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
BlockClosure>>on:do:
NBRecursionDetect class>>in:during:
NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode:
NBFFICalloutAPI>>function:emit:
NativeBoostMac32(NativeBoost)>>loadModule:
CairoLibraryLoader class>>loadCairoLibrary
CairoLibraryLoader class>>getLibraryHandle
AthensCairoSurface class>>nbLibraryNameOrHandle
AthensCairoSurface class(Object)>>nbCall:
AthensCairoSurface class>>primImage:width:height:
AthensCairoSurface class>>extent:format:
AthensCairoSurface class>>extent:
TRCanvas>>initialize
TRCanvas class(Behavior)>>new
RTView>>initialize
RTView class(Behavior)>>new
R3View>>initialize
R3View class(Behavior)>>new
Roassal3DModel>>initialize
Roassal3DModel class(Behavior)>>new
Roassal3DModel class(ComposableModel class)>>owner:
CityBrowser(ComposableModel)>>instantiate:
CityBrowser>>initializeWidgets
CityBrowser(ComposableModel)>>initialize
CityBrowser class(Behavior)>>new
CityBrowser class(ComposableModel class)>>owner:
VidiBrowser(ComposableModel)>>instantiate:
VidiBrowser>>initializeWidgets
VidiBrowser(ComposableModel)>>initialize
VidiBrowser>>initialize
VidiBrowser class(Behavior)>>new
ReModel>>vidi
VidiSession>>openVidi
[ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction
self value.
Processor terminateActive ] in BlockClosure>>newProcess

===========================================


Thank you.

2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

now ViDI should work. I haven’t been working on it for a while, but feel free to report more issues, as I’ll get back to it soon.

Uko



On 24 Apr 2015, at 09:57, Rafael Luque <[hidden email]> wrote:

Thank you! I'm looking forward to hearing from you about the new version.

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko



On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.






Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Rafael Luque
Hi Yuriy,

I've tried with the latest changes but the problem described in my previous email still persists:

"Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

All your recommendations will be very welcomed.

Thank you.

Rafa



2015-04-24 18:13 GMT+02:00 Rafael Luque <[hidden email]>:
Hi Uko

I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

This is the stack trace for your information:

===========================================

NBFFICallout>>loaderForArgNamed:
NBFFICallout>>loaderForArgNamed:indirectIndex:
NBFFICallout>>argName:indirectIndex:type:ptrArity:
NBFnSpecParser>>parseArgument
NBFnSpecParser>>parseArguments
NBFnSpecParser>>parseAnonFunction:
NBFFICallout>>anonSpec:
[ :t3 | 
t3
useEmitCall;
callType: conv;
sender: context;
parseOptions: options;
anonSpec: t1;
generate: t2 ] in NBFFICalloutAPI>>function:emit:
[ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
BlockClosure>>on:do:
NBRecursionDetect class>>in:during:
NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode:
NBFFICalloutAPI>>function:emit:
NativeBoostMac32(NativeBoost)>>loadModule:
CairoLibraryLoader class>>loadCairoLibrary
CairoLibraryLoader class>>getLibraryHandle
AthensCairoSurface class>>nbLibraryNameOrHandle
AthensCairoSurface class(Object)>>nbCall:
AthensCairoSurface class>>primImage:width:height:
AthensCairoSurface class>>extent:format:
AthensCairoSurface class>>extent:
TRCanvas>>initialize
TRCanvas class(Behavior)>>new
RTView>>initialize
RTView class(Behavior)>>new
R3View>>initialize
R3View class(Behavior)>>new
Roassal3DModel>>initialize
Roassal3DModel class(Behavior)>>new
Roassal3DModel class(ComposableModel class)>>owner:
CityBrowser(ComposableModel)>>instantiate:
CityBrowser>>initializeWidgets
CityBrowser(ComposableModel)>>initialize
CityBrowser class(Behavior)>>new
CityBrowser class(ComposableModel class)>>owner:
VidiBrowser(ComposableModel)>>instantiate:
VidiBrowser>>initializeWidgets
VidiBrowser(ComposableModel)>>initialize
VidiBrowser>>initialize
VidiBrowser class(Behavior)>>new
ReModel>>vidi
VidiSession>>openVidi
[ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction
self value.
Processor terminateActive ] in BlockClosure>>newProcess

===========================================


Thank you.

2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

now ViDI should work. I haven’t been working on it for a while, but feel free to report more issues, as I’ll get back to it soon.

Uko



On 24 Apr 2015, at 09:57, Rafael Luque <[hidden email]> wrote:

Thank you! I'm looking forward to hearing from you about the new version.

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko



On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.







Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Uko2
Alex, Ronie,

do you have any idea what can cause the issue? Because I’ve never worked with native boost.

Uko


On 28 Jul 2015, at 20:52, Rafael Luque <[hidden email]> wrote:

Hi Yuriy,

I've tried with the latest changes but the problem described in my previous email still persists:

"Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

All your recommendations will be very welcomed.

Thank you.

Rafa



2015-04-24 18:13 GMT+02:00 Rafael Luque <[hidden email]>:
Hi Uko

I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

This is the stack trace for your information:

===========================================

NBFFICallout>>loaderForArgNamed:
NBFFICallout>>loaderForArgNamed:indirectIndex:
NBFFICallout>>argName:indirectIndex:type:ptrArity:
NBFnSpecParser>>parseArgument
NBFnSpecParser>>parseArguments
NBFnSpecParser>>parseAnonFunction:
NBFFICallout>>anonSpec:
[ :t3 | 
t3
useEmitCall;
callType: conv;
sender: context;
parseOptions: options;
anonSpec: t1;
generate: t2 ] in NBFFICalloutAPI>>function:emit:
[ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
BlockClosure>>on:do:
NBRecursionDetect class>>in:during:
NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode:
NBFFICalloutAPI>>function:emit:
NativeBoostMac32(NativeBoost)>>loadModule:
CairoLibraryLoader class>>loadCairoLibrary
CairoLibraryLoader class>>getLibraryHandle
AthensCairoSurface class>>nbLibraryNameOrHandle
AthensCairoSurface class(Object)>>nbCall:
AthensCairoSurface class>>primImage:width:height:
AthensCairoSurface class>>extent:format:
AthensCairoSurface class>>extent:
TRCanvas>>initialize
TRCanvas class(Behavior)>>new
RTView>>initialize
RTView class(Behavior)>>new
R3View>>initialize
R3View class(Behavior)>>new
Roassal3DModel>>initialize
Roassal3DModel class(Behavior)>>new
Roassal3DModel class(ComposableModel class)>>owner:
CityBrowser(ComposableModel)>>instantiate:
CityBrowser>>initializeWidgets
CityBrowser(ComposableModel)>>initialize
CityBrowser class(Behavior)>>new
CityBrowser class(ComposableModel class)>>owner:
VidiBrowser(ComposableModel)>>instantiate:
VidiBrowser>>initializeWidgets
VidiBrowser(ComposableModel)>>initialize
VidiBrowser>>initialize
VidiBrowser class(Behavior)>>new
ReModel>>vidi
VidiSession>>openVidi
[ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction
self value.
Processor terminateActive ] in BlockClosure>>newProcess

===========================================


Thank you.

2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

now ViDI should work. I haven’t been working on it for a while, but feel free to report more issues, as I’ll get back to it soon.

Uko



On 24 Apr 2015, at 09:57, Rafael Luque <[hidden email]> wrote:

Thank you! I'm looking forward to hearing from you about the new version.

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko



On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.








Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

abergel
NativeBoost create this kind of error if you have the .sources file that is missing. 
Are you sure this is not the case?

Alexandre
-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.



On Jul 28, 2015, at 5:08 PM, Yuriy Tymchuk <[hidden email]> wrote:

Alex, Ronie,

do you have any idea what can cause the issue? Because I’ve never worked with native boost.

Uko


On 28 Jul 2015, at 20:52, Rafael Luque <[hidden email]> wrote:

Hi Yuriy,

I've tried with the latest changes but the problem described in my previous email still persists:

"Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

All your recommendations will be very welcomed.

Thank you.

Rafa



2015-04-24 18:13 GMT+02:00 Rafael Luque <[hidden email]>:
Hi Uko

I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

This is the stack trace for your information:

===========================================

NBFFICallout>>loaderForArgNamed:
NBFFICallout>>loaderForArgNamed:indirectIndex:
NBFFICallout>>argName:indirectIndex:type:ptrArity:
NBFnSpecParser>>parseArgument
NBFnSpecParser>>parseArguments
NBFnSpecParser>>parseAnonFunction:
NBFFICallout>>anonSpec:
[ :t3 | 
t3
useEmitCall;
callType: conv;
sender: context;
parseOptions: options;
anonSpec: t1;
generate: t2 ] in NBFFICalloutAPI>>function:emit:
[ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
BlockClosure>>on:do:
NBRecursionDetect class>>in:during:
NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:
NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode:
NBFFICalloutAPI>>function:emit:
NativeBoostMac32(NativeBoost)>>loadModule:
CairoLibraryLoader class>>loadCairoLibrary
CairoLibraryLoader class>>getLibraryHandle
AthensCairoSurface class>>nbLibraryNameOrHandle
AthensCairoSurface class(Object)>>nbCall:
AthensCairoSurface class>>primImage:width:height:
AthensCairoSurface class>>extent:format:
AthensCairoSurface class>>extent:
TRCanvas>>initialize
TRCanvas class(Behavior)>>new
RTView>>initialize
RTView class(Behavior)>>new
R3View>>initialize
R3View class(Behavior)>>new
Roassal3DModel>>initialize
Roassal3DModel class(Behavior)>>new
Roassal3DModel class(ComposableModel class)>>owner:
CityBrowser(ComposableModel)>>instantiate:
CityBrowser>>initializeWidgets
CityBrowser(ComposableModel)>>initialize
CityBrowser class(Behavior)>>new
CityBrowser class(ComposableModel class)>>owner:
VidiBrowser(ComposableModel)>>instantiate:
VidiBrowser>>initializeWidgets
VidiBrowser(ComposableModel)>>initialize
VidiBrowser>>initialize
VidiBrowser class(Behavior)>>new
ReModel>>vidi
VidiSession>>openVidi
[ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction
self value.
Processor terminateActive ] in BlockClosure>>newProcess

===========================================


Thank you.

2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

now ViDI should work. I haven’t been working on it for a while, but feel free to report more issues, as I’ll get back to it soon.

Uko



On 24 Apr 2015, at 09:57, Rafael Luque <[hidden email]> wrote:

Thank you! I'm looking forward to hearing from you about the new version.

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

Uko



On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

Thanks

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:
Hi Rafael,

I will take a look. Which operating system are you using?

Uko

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

When I launch a review session over any package I always get the following error:

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

Thank you.









Reply | Threaded
Open this post in threaded view
|

Re: ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

Blondeau Vincent
In reply to this post by Uko2

Hi Yuriy,

 

You have to put the library used by native boost in the VM folder (ie. *.so or *.dll). It should do the trick.

 

Vincent

 

De : Pharo-users [mailto:[hidden email]] De la part de Yuriy Tymchuk
Envoyé : mardi 28 juil
let 2015 22:08
À : Any question about pharo is welcome
Objet : Re: [Pharo-users] ViDI error: variable named "aModuleName" in NativeBoost>>#loadModule:

 

Alex, Ronie,

 

do you have any idea what can cause the issue? Because I’ve never worked with native boost.

 

Uko

 

 

On 28 Jul 2015, at 20:52, Rafael Luque <[hidden email]> wrote:

 

Hi Yuriy,

 

I've tried with the latest changes but the problem described in my previous email still persists:

 

"Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

 

All your recommendations will be very welcomed.

 

Thank you.

 

Rafa

 

 

 

2015-04-24 18:13 GMT+02:00 Rafael Luque <[hidden email]>:

Hi Uko

 

I've just tried with your last changes, but I get the same error: "Error: Could not find accessor for variable named "aModuleName" in NativeBoost>>#loadModule:"

 

This is the stack trace for your information:

 

===========================================

 

NBFFICallout>>loaderForArgNamed:

NBFFICallout>>loaderForArgNamed:indirectIndex:

NBFFICallout>>argName:indirectIndex:type:ptrArity:

NBFnSpecParser>>parseArgument

NBFnSpecParser>>parseArguments

NBFnSpecParser>>parseAnonFunction:

NBFFICallout>>anonSpec:

[ :t3 | 

t3

useEmitCall;

callType: conv;

sender: context;

parseOptions: options;

anonSpec: t1;

generate: t2 ] in NBFFICalloutAPI>>function:emit:

[ t6 := t1 value: (self newForMethod: t3) ] in NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:

BlockClosure>>on:do:

NBRecursionDetect class>>in:during:

NBFFICallout class(NBNativeCodeGen class)>>generateCode:andRetry:

NBFFICallout class(NBNativeCodeGen class)>>handleFailureIn:nativeCode:

NBFFICalloutAPI>>function:emit:

NativeBoostMac32(NativeBoost)>>loadModule:

CairoLibraryLoader class>>loadCairoLibrary

CairoLibraryLoader class>>getLibraryHandle

AthensCairoSurface class>>nbLibraryNameOrHandle

AthensCairoSurface class(Object)>>nbCall:

AthensCairoSurface class>>primImage:width:height:

AthensCairoSurface class>>extent:format:

AthensCairoSurface class>>extent:

TRCanvas>>initialize

TRCanvas class(Behavior)>>new

RTView>>initialize

RTView class(Behavior)>>new

R3View>>initialize

R3View class(Behavior)>>new

Roassal3DModel>>initialize

Roassal3DModel class(Behavior)>>new

Roassal3DModel class(ComposableModel class)>>owner:

CityBrowser(ComposableModel)>>instantiate:

CityBrowser>>initializeWidgets

CityBrowser(ComposableModel)>>initialize

CityBrowser class(Behavior)>>new

CityBrowser class(ComposableModel class)>>owner:

VidiBrowser(ComposableModel)>>instantiate:

VidiBrowser>>initializeWidgets

VidiBrowser(ComposableModel)>>initialize

VidiBrowser>>initialize

VidiBrowser class(Behavior)>>new

ReModel>>vidi

VidiSession>>openVidi

[ (VidiSessionManager default newSessionOnPackages: packages) openVidi ] in VidiSessionPackagesSelect>>nextAction

self value.

Processor terminateActive ] in BlockClosure>>newProcess

 

===========================================

 

 

Thank you.

 

2015-04-24 14:25 GMT+02:00 Yuriy Tymchuk <[hidden email]>:

Hi Rafael,

 

now ViDI should work. I haven’t been working on it for a while, but feel free to report more issues, as I’ll get back to it soon.

 

Uko

 

 

 

On 24 Apr 2015, at 09:57, Rafael Luque <[hidden email]> wrote:

 

Thank you! I'm looking forward to hearing from you about the new version.

 

2015-04-24 9:52 GMT+02:00 Yuriy Tymchuk <[hidden email]>:

Ok, I found the problem. Some Spec api changed. I stable version will work at least on Mac quite soon. :)

 

Uko

 

 

 

On 23 Apr 2015, at 17:46, Rafael Luque <[hidden email]> wrote:

 

I'd like to use it in a Linux box, but as you told me Linux is not yet supported, I'm using a Mac OS X Yosemite (version 10.10.2).

 

Thanks

 

2015-04-23 17:37 GMT+02:00 Yuriy Tymchuk <[hidden email]>:

Hi Rafael,

 

I will take a look. Which operating system are you using?

 

Uko

 

On 23 Apr 2015, at 17:30, Rafael Luque <[hidden email]> wrote:

 

Hi,

I installed ViDI on Pharo 4 following the project instructions detailed in its GitHub page:

Gofer new
  smalltalkhubUser: 'YuriyTymchuk'
  project: 'Configuration';
  configurationOf: 'Vidi';
  load.
#ConfigurationOfVidi asClass loadStable

 

When I launch a review session over any package I always get the following error:

 

"Could not find accesor for variable named "aModuleName" in NativeBoost>>#loadModule:"

 

I'm very interested in this kind of quality assurance tools, so any help will be very welcomed.

 

Thank you.

 

 

 

 

 

 

 

 




Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité de Worldline ne pourra être recherchée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être recherchée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Worldline liability cannot be triggered for the message content. Although the sender endeavours to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.