Le forum de XCAS

Hi,

since it already happened the second time today, I guess there may be a problem with updating the Windows versions of Xcas!?

The first time it happened on 13.Dec.: although the filedates of xcasinst.exe (and xcasunst.exe) have changed to 13.Dec., after unpacking I got the old version of one day earlier (from 12.Dec).

Now today the same problem: both installers show 17.Dec., but after installation (or manually extracting) I get exactly the same files as the 12.Dec. version (xcas.exe, giac.exe, giac.dll etc. ...).

If the Windows version won't have changed you would probably not have updated these installation files at all, so I guess that there's indeed something wrong with building the Windows packages now?

Regards,
Franz

Very strange, because I think I tried version() and got 1.1.3-14 before uploading the installers.
What happens if you type version()?

parisse a écrit :Very strange, because I think I tried version() and got 1.1.3-14 before uploading the installers.
What happens if you type version()?

I get 1.1.3-12.
But that's clear because the files are identical (size and date), I've even made a byte-compare.
It's just the version of 12.Dec.

Franz

Thanks for reporting, should be fixed now!

parisse a écrit :Thanks for reporting, should be fixed now!

Yes, at least it seems so.
Xcas itself is still reporting 1.1.3-12, but version() says giac 1.1.3-14, so I guess it's ok.

Thanks,
Franz

Yes, one file was not recompiled after version number change.

Same problem now reappearing again:
yesterday and today new (?) xcasinst updates, but just exactly the versions from 9.Jan.
There seems to be something seriously broken with your build process.

Edit: Fixed, now it's a new version, thanks!

Franz

No, the build is ok, but I copied the wrong file...

Just a question:
is it ok that xcas.exe is still dated 15.2.2015, when the other files (giac.exe/dll) are updated with todays date 25.2.2015?

Franz

No, thanks for checking, should be fixed now.

parisse a écrit :No, thanks for checking, should be fixed now.

Yes, it's up-to-date now, thanks!

Franz