Feature freeze is over - FreeCAD 0.20 was released
Forum rules
Be nice to others! Respect the FreeCAD code of conduct!
Be nice to others! Respect the FreeCAD code of conduct!
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Still in feature freeze - FreeCAD 0.20 was released
0.20 stable flatpak is also available now
Re: Still in feature freeze - FreeCAD 0.20 was released
Great. So I can and will now make the announcement on the user's forum.
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Still in feature freeze - FreeCAD 0.20 was released
@chennes you mentioned before that you could sign our macOS packages, is that done for the 0.20 dmg? I'm not an apple user but I think usually people are presented with scary messages about the app not being signed and then need to jump through some hoops to allow running the app, could this be solved by you signing that package?
Re: Still in feature freeze - FreeCAD 0.20 was released
The DMG was created by @looo . looo, can you please have a look?adrianinsaval wrote: ↑Thu Jun 16, 2022 3:40 pm @chennes you mentioned before that you could sign our macOS packages, is that done for the 0.20 dmg? I'm not an apple user but I think usually people are presented with scary messages about the app not being signed and then need to jump through some hoops to allow running the app, could this be solved by you signing that package?
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Still in feature freeze - FreeCAD 0.20 was released
Yes but I'm not sure if his signature would be valid to apple, I asked chennes because of this: https://github.com/FreeCAD/FPA/issues/6 ... 1151157999
As mentioned there it would be best to have an official FreeCAD signature but signed by chennes is better than not signed IMO
As mentioned there it would be best to have an official FreeCAD signature but signed by chennes is better than not signed IMO
Re: Still in feature freeze - FreeCAD 0.20 was released
If @looo has instructions on how I can compile to generate the same version he is generating, then I can use my copy of Xcode to produce a new, signed executable. I don't think he's doing it exactly the same way as it's described on the Wiki, right? Once we have a signed binary I can also try to get it published on the Apple App Store so there is a slightly more official (and free!) version up there.
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Still in feature freeze - FreeCAD 0.20 was released
It's done through conda, do you need a way to build freecad or just the package? I think this is how it's built: https://github.com/looooo/freecad-feeds ... x_build.sh and this is how it's bundled: https://github.com/FreeCAD/FreeCAD-Bund ... _bundle.sh
probably better to look how this scripts are called in case they need prior setups
probably better to look how this scripts are called in case they need prior setups
Are there other (scam) versions published in the apple store too?
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: Still in feature freeze - FreeCAD 0.20 was released
@yorik sorry to bother but I feel like this statement in your blog is inaccurate:
While you can open 0.20 files in 0.19 some features are just not compatible and won't recompute properly, easiest example being PD tapered pads, not really sure if there are other stuff like this. Reagrding the config and add-ons this is plain wrong for Linux! And possibly mac although I'm not sure, as you may know the config, data cache directories were changed to follow the xdg specification, old configs, addons and macros do NOT get auto copied tot he new locations, some of the dev releases did copy the data but this was later removed so this might have made you think that.which means the files you produce with 0.20 are still 100% openable with 0.19. Your settings, configurations and add-ons will be kept when you upgrade from 0.19 to 0.20.
Re: Still in feature freeze - FreeCAD 0.20 was released
Hmm you are right. I'll amend
We should document the linux path change somewhere...
We should document the linux path change somewhere...