For 4D v19, we started a long-term refinement of our logs. Our first effort was to improve their format to give you better and clearer information. As for 4D v19 R3, we added 2 new functionalities: the ability to instantly pause logging and a way for support teams to easily help their customers configure their logs through a configuration file.
The release of Silicon Macs had a great impact on the way 4D compiles applications. Before v19, 4D was compiling only for Intel architecture, using the same code on Mac and Windows. But Silicon Macs use a new architecture, and as such 4D needs to compile specifically for Silicon. It affects cross-platform client/server application building.
As long as you build your server on Mac, it’s not much of an issue, as you can compile for both Intel and Silicon platforms. But on Windows, it’s not possible to compile for Silicon Macs. Our current recommendation is to compile the project on Mac for both architectures, and then copy it on a Windows machine before building the server. Unfortunately, for big projects with a lot of data, the copy can take some time.
On Mac, application signature has become a standard, and since Big Sur, you can’t even run unsigned applications. In the past, we published a workaround to build client-server applications running on a Windows server and accepting connections from Mac clients. With the release of 4D v19, we have updated the application building in 4D to handle this case. Here is how you can build a single platform or a cross-platform application in v19.
We recently reviewed the formats of our logs to increase their readability and their compliance with automated analysis. We made these improvements in response to real-life situations we experienced, directly addressing issues that were hindering our ability to use 4D logs. In this blog post, we’ll explain in detail what changes we made so you can adjust your log analyzing tools accordingly.
We already introduced you to our new Silicon compiler in a previous blog post. This new compiler will be used to build Silicon native applications and will be available only in project mode.
Intel native applications (on Windows and Mac) will continue to use the classic compiler.
Let’s dig deeper and see exactly how it works.
Apple’s groundbreaking release of the new Silicon Macs pushed us to release 4D v19 six months earlier to provide you with a Silicon native version of 4D as soon as possible. We reviewed all our code, ensuring its compatibility with Silicon, performed extensive testing on this new platform, and we’re finally ready to provide you with the first Silicon native version of 4D. Let me guide you through this revolution!
Since Apple’s first announcement about Silicon, we’ve been keeping you informed through a series of blog posts and this post is no different!
So what’s going on? Well, the first Silicon Macs equipped with the brand new M1 chip are now available on the market. Here are two important pieces of information we need to share with you:
In a previous blog post, we introduced you to the new Silicon Macs that Apple is launching at the end of this year, as well as our plans to smoothly transition your 4D applications to them.
These new Macs use a new type of processor: ARM processors from the same family Apple uses in iPhones and iPads. A new processor family means a new instruction set and, for us here at 4D, a new compiler.
At the annual Worldwide Developers Conference (WWDC2020), Apple announced the release of a brand new processor technology called Apple Silicon.
In this blog post, we’ll introduce you to this new technology and tell you about our plans to smoothly transition your 4D applications to Silicon.
Got a question, suggestion or just want to get in touch with the 4D bloggers? Drop us a line!
* Your privacy is very important to us. Please click here to view our Policy