Hi Vincent, Indeed your Cruiser tool proved very useful! It showed me how to implement some absolutely required aspects of packaging, in pharo 6.1 (i.e. the NoDebugger trick).
I tried also to get this independence of FFI of the sources working, by simply filing in the attached code (from P7) into P6.1. However this didn’t appear to do the job – maybe some additional actions are required (recompiling things?)? Hans From: vincent.blond...@lamresearch.com <vincent.blond...@lamresearch.com> Sent: woensdag 21 november 2018 3:33 To: pharo-users@lists.pharo.org Subject: Re: [Pharo-users] problem when running without changes file (on windows) Hi, You may want to look at https://github.com/VincentBlondeau/Cruiser that contains all the actions needed to perform a clean packaging (Still in dev though). The only issue is that it works for Pharo 7 only and you’ll need to backport changes (I can help you on that). Some changes are related to new VM primitives so you have to use the current stable one (which should also running the Pharo 6.1 images). Don’t hesitate to ask me if you need advices or help on this. I could try to make the tool work on Pharo 6, but it could be incomplete especially on the FFI and stdio part. HTH, Cheers, Vincent From: Pharo-users <pharo-users-boun...@lists.pharo.org<mailto:pharo-users-boun...@lists.pharo.org>> On Behalf Of Guillermo Polito Sent: Wednesday, November 14, 2018 6:04 To: Any question about pharo is welcome <pharo-users@lists.pharo.org<mailto:pharo-users@lists.pharo.org>> Subject: Re: [Pharo-users] problem when running without changes file (on windows) Hi Hans, On Wed, Nov 14, 2018 at 2:56 PM Baveco, Hans <hans.bav...@wur.nl<mailto:hans.bav...@wur.nl>> wrote: Ok, thanks for this crucial information! Would backporting be as simple as filing out the class and the single method from Pharo7 and filing in in Pharo6.1 ? (probably not) While not completely sure, I think they actually could work. Maybe you found in the way a couple of other methods to backport, but I think that it should not be that difficult. This is the original issue that fixed this in Pharo7: https://pharo.fogbugz.com/f/cases/21124/FFI-should-work-without-the-sources<https://urldefense.proofpoint.com/v2/url?u=https-3A__pharo.fogbugz.com_f_cases_21124_FFI-2Dshould-2Dwork-2Dwithout-2Dthe-2Dsources&d=DwMFaQ&c=RWI7EqL8K9lqtga8KxgfzvOYoob76EZWE0yAO85PVMQ&r=kIZIYXBAA3fhM7P5HOuTC5w6mnEApTfXPTq3lR34ZiY&m=zueS3nflFQs72ZqbAT4is78d2UpD9JXXi7jAp6Luxok&s=Gt8I-Pl8yzIRifPtshzLQaSp6N32UNhEcPVLmdyrYIg&e=> And here the PR with the fix: https://github.com/pharo-project/pharo/pull/739<https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_pharo-2Dproject_pharo_pull_739&d=DwMFaQ&c=RWI7EqL8K9lqtga8KxgfzvOYoob76EZWE0yAO85PVMQ&r=kIZIYXBAA3fhM7P5HOuTC5w6mnEApTfXPTq3lR34ZiY&m=zueS3nflFQs72ZqbAT4is78d2UpD9JXXi7jAp6Luxok&s=Omu3Ix_N-j7eA6wU7S1AhC5mhH51qh8rmDonNQzete0&e=> There are a couple of more changes there, but not so many.
FFICompilerPlugin.st
Description: FFICompilerPlugin.st
RBMethodNode-ensureCachedArgumentNames.st
Description: RBMethodNode-ensureCachedArgumentNames.st
CompilationContext class-addDefaultTransformationPlugin.st
Description: CompilationContext class-addDefaultTransformationPlugin.st
CompilationContext class-defaultTransformationPlugins.st
Description: CompilationContext class-defaultTransformationPlugins.st
