Hi Thomas On Thursday, April 2, 2020 at 11:35:55 AM UTC-3, javier hector wrote: > > > Hi Thomas, > On Thursday, April 2, 2020 at 8:13:27 AM UTC-3, Thomas Beale wrote: >> >> Hi Javier, >> the behaviour of git_status changes depending on how I build it. >> >> If a do a build from scratch and then

Eric, I agree with all of that. - thomas On Wednesday, 1 April 2020 23:56:57 UTC+1, Eric Bezault wrote: > > On 01/04/2020 23:40, Thomas Beale wrote: > > Hi Alex, > > > > I was just contemplating this: > > |⟳c:s ¦print (c.name)⟲| > > > > Why not just use the initial symbol, and forget the

Hi Thomas, On Thursday, April 2, 2020 at 8:13:27 AM UTC-3, Thomas Beale wrote: > > Hi Javier, > the behaviour of git_status changes depending on how I build it. > > If a do a build from scratch and then finalise (from inside Estudio) WITH > assertions (whatever is enabled in the .ecf, I didn't

Hi Javier, the behaviour of git_status changes depending on how I build it. If a do a build from scratch and then finalise (from inside Estudio) WITH assertions (whatever is enabled in the .ecf, I didn't change anything), I get a binary that works (except the final line is still missing an LF):

Hi Thomas, On Wednesday, April 1, 2020 at 5:40:58 PM UTC-3, Thomas Beale wrote: > > Hi Javier, > > initial experiments don't get the results I would expect. > > First with git_status: > > thomas@Meduse-VB:~/openEHR-specifications/specifications-AM$ git_status -- > porcelain > > Intializing Libgit2

This could only work if we restrict this notation to only one instruction. So the following: ⟳ c: s ¦ print (c.name); print ("%N") would be a loop followed by an instruction to print a newline (and not a loop with two instructions). Personally, this would have my preference. I think

Hi Alex, I was just contemplating this: ⟳ c: s ¦ print (c.name) ⟲ Why not just use the initial symbol, and forget the final one, i.e. ⟳ c: s ¦ print (c.name) That seems more consistent with the other operators. - thomas On Tuesday, 17 March 2020 12:19:06 UTC, Alexander Kogtenkov wrote: > >

Hi Javier, initial experiments don't get the results I would expect. First with git_status: thomas@Meduse-VB:~/openEHR-specifications/specifications-AM$ git_status -- porcelain Intializing Libgit2 M docs/ADL2/master04-cadl.adoc M docs/ADL2/master04-cadl.adoc M docs/ADL2/master04-cadl.ad

Great, I will add it ASAP > > > Thanks very much for the quick help. > You are welcome > - thomas >

I think I am there... I can compile and finalise the git_status example. However, when I run it from the command line, I get the following thomas@Meduse-VB:~/Eiffel/eiffel-wrap-c/wrap_libgit2$ git_status git_status: error while loading shared libraries: libgit2.so.0.99: cannot open shared

Hi Thomas, On Wednesday, April 1, 2020 at 7:00:25 AM UTC-3, Thomas Beale wrote: > > Getting closer... > now when using wrap_c, according to the wrap_libgit2 README, I get: > Ok I see there is an issue in the README file, i've fixed it now The command line should be wrap_c --verbose --output-dir=

Getting closer... now when using wrap_c, according to the wrap_libgit2 README, I get: thomas@Meduse-VB:~/Eiffel/eiffel-wrap-c/wrap_libgit2$ wrap_c --verbose --output-dir=$LIB_PATH/library/generated_wrapper --full-header=$LIB_PATH/library/C/include/git2.h config.xml [100%] phase 1: parsing

Hi Thomas, I´ve fixed the issue. Please check the latest code https://github.com/eiffel-wrap-c/WrapC Javier On Tuesday, March 31, 2020 at 5:20:15 PM UTC-3, Thomas Beale wrote: > > Hi Javier, > I finally got around to trying this. > I have built libgit2 according to the README; it installs a

Hi Thomas thanks for reporting the issue, I didn't notice the issue with Eiffel 19.05. I'will fix it ASAP. On Tuesday, March 31, 2020 at 5:20:15 PM UTC-3, Thomas Beale wrote: > > Hi Javier, > I finally got around to trying this. > I have built libgit2 according to the README; it installs a .so

Hi Javier, I finally got around to trying this. I have built libgit2 according to the README; it installs a .so and a .a (when I did a static build as well) into /usr/local/lib: thomas@Meduse-VB:~/Eiffel/eiffel-wrap-c/libgit2/build$ ls /usr/local/lib/*git* /usr/local/lib/libgit2.a /usr/local/l

I did finally figure it out ... but if the implementation isn't finished, probably it should not be an option there in the libraries? (It doesn't compile at any rate). On Tuesday, 31 March 2020 18:22:54 UTC+1, Jocelyn Fiat wrote: > > If you look at the vision2.ecf file, you will see the variable

If you look at the vision2.ecf file, you will see the variable "vision_implementation" so you should put in your application target the line However, I fear the gtk3 implementation has never been completed. Regards, -- Jocelyn On Tue, Mar

I see there is a GTK3.4 implementation of Vision2. Is there any documentation about what it fixes compared to GTK2? And how do I enabled it? I assume something like the following:

Typo... not but presumably something like but I don't know what the xxx is. On Tuesday, 31 March 2020 18:07:17 UTC+1, Thomas Beale wrote: > > I see there is a GTK3.4 implementation of Vision2.

This new release of Gobo Eiffel should work fine with EiffelStudio 19.05 and 19.12. Please see the release notes here: https://github.com/gobo-eiffel/gobo/blob/master/History.md You can download the Gobo package from SourceForge: https://sourceforge.net/projects/gobo-eiffel/files/gobo

I have started Eiffel Studio on RPI4 with armv7 and it runs quite well, but the compilation is slow. Spent several day to put Eiffel Studio cross-compiler for armv7 to run on Linux PC (there is a mix of old and new information on cross compiling on eiffel.org) And did Wrap_C on PIGPIO library.

For info, I have been using/testing using the Raspberry pi 4 (4GB), and EiffelStudio runs well on it. For smaller raspberry pi such as RPI v1, I mostly used the command line compiler, especially to build the armv6 version. But EiffelStudio should work, however maybe not as reactive as you wish.

So great!!!! I rejoice testing it!! Thx Larry always had this question. Maybe if somebody can let a project on youtube it could do some publicity for Eiffel ... On Wed, Mar 18, 2020 at 7:12 AM Jocelyn Fiat wrote: > And also ARMv7 for latest Raspberry Pi. > > On Wed, Mar 18,

And also ARMv7 for latest Raspberry Pi. On Wed, Mar 18, 2020 at 8:11 AM Jocelyn Fiat wrote: > Yes. > > On Tue, Mar 17, 2020 at 11:54 PM Larry Rix > wrote: > >> I noted on the Linux Requirements on Eiffel.org that ARMv6 is listed as >> being

Yes. On Tue, Mar 17, 2020 at 11:54 PM Larry Rix wrote: > I noted on the Linux Requirements on Eiffel.org that ARMv6 is listed as > being compatible with the EiffelStudio 19.05 > > Does this mean I can successfully install ES on a Raspberry Pi with > Raspbian