The latest FastMM version is 4.991
Delphi XE8 uses FastMM but which version is that?
The version of FastMM that ships as the built-in Delphi memory manager is a customised version that does not correspond to any version from the official FastMM code base. This customised version is cut down and has significantly reduced functionality.
Embarcadero maintains that customised version, and you can inspect it by examining the file <installdir>\source\rtl\sys\getmem.inc. To the best of my knowledge, the Embarcadero version was forked from the official project some time ago and there is a significant divergence.
Related
I have taken a look at these URLs:
check if runtime installed
https://learn.microsoft.com/en-us/microsoft-edge/webview2/concepts/distribution
some sample code assuming newer Delphi
Using WebView (EdgeHTML) in Delphi / C++ Builder
some sample code assuming newer Delphi
WebView2 (TEdgeBrowser) updated Delphi interface (e.g. ICoreWebView2Controller2)
Yet even those seem to assume a newer Delphi version than I use (XE4) ... and preferably I would like Lazarus support as well. At the same time I really love being able to use "newest available patched system browser" which is why I am not jumping on https://github.com/salvadordf/CEF4Delphi albeit it may end up being the final solution.
Is there anyone else who has begun the undertaking of implementing webview2 on older versions or is this simply impractical due to type libraries not being importable etc? (i.e. major headache in converting, implementing and testing everything, furthermore on old Delphi versions)
I recently published WebView4Delphi at GitHub with an MIT license.
WebView4Delphi uses the WebView2 runtime to embed Chromium based browsers in Delphi and Lazarus applications.
It was developed in Delphi 11 but it also works with Delphi XE3.
Anybody know if delphi xe7 compatible with windows 10?
Embarcadero says that XE8 is compatible. But tells nothing about XE7.
Yes, you can install XE7 on Windows 10, and the executables that it produces are compatible with Windows 10.
Embarcadero have been producing a lot of marketing recently that implies that you need XE8 to do Windows 10 development. Truth be told, you can use any version of Delphi beyond Delphi 1. Of course the newer versions make life easier, and clearly you need XE2 or later to target 64 bit executables.
So far as I can see, the only Windows 10 specific feature that is offered with XE8 is a Windows 10 style. That was what I took from a conversation with Marco Cantú on the subject. I guess that would be useful for FMX targets. If you are targeting classic VCL apps, and use the standard system theme, then this is of no interest. There's no point at all in faking the system style when you can let the system give you the true style. My old Delphi 6 applications, built with Mike Lischke's theme manager code, look and feel on Windows 10 identical to an application built with XE8.
Although Embarcadero says that XE8 is compatible with Windows 10, I'm unable to install or load our existing bpl projects using XE8 with Windows 10.
I moved to XE8 because our projects wouldn't build with Windows 10 using XE4.
You can install and run Delphi XE7 on a Windows 10 machine. And of course you can compile your projects on Windows 10.
But there were no enhancements made in the VCL or FireMonkey towards the new operating system. There is no official support for Windows 10. Your applications may not look and feel 100% like other applications do on Windows 10. But they can still be run as long as long as they don't use any old API that is no longer supported on Windows 10.
You can install and run Delphi XE7 on a Windows 10 machine.
I have to update a Delphi XE installation for a project to a newer version of Delphi but I don't have much experience with Delphi, the problem is there are plenty of old packages and components in there.
When I install a new version did I have to install all components again (if it possible to install it in this new version) or is it something like an update to my old installation and all installed stuff is now in the new version also?
Updating a Delphi XE application to a newer Delphi is usually quite easy. The only serious issue could be third party components which you must install in the newer Delphi version. Check with each component vendor that a version exists for your target Delphi version.
I always strongly recommand to NOT use any third party component that has no source available. Also don't buy any third party component using a DLL, OCX or other external binary object.
When you buy a third party component, always buy the source code with it. Then throw away any pre-build package or dcu and recompile everything before any serious use. That way you'll be sure to have all required source code and work with that source code.
Once you have the source code, it becomes much easier to port to the next Delphi version. Usually there is just nothing to change (There was only one notable exception in the past between Delphi 2007 and Delphi 2010 when Unicode string were introduced).
When there is something to change, it is usually only the name of a "used" unit. Somtimes Embarcadero move one class from a unit to another one. Sometimes, you have to change a $IFDEF which specify a Delphi version. Look at {$IFDEF VER180} and similar to adapt to you current version (See the online help for such symbol).
And if you still have issues, then ask here...
Upgrading to newer version of Delphi might not be a trivial task.
First problem you will run into are Thid Party Components.
If you don't own the souce code for them it means that they come with precompiled packages and these packages unfortunately arent compatible between different Delphi versions.
If you do have source code for them you might be able to recompile them on newer Delphi versions but this might require you to do some code changes.
So I strongly recomend you first check to see if there are updated versions of these components available that support the Delphi version to which you are planning to upgrade.
For instance if your application relies on BDE (Borland Database Engine) that shipped with older versions of Delphi you Will be forced to do Quite some changes to properly set up the FireDac database framework that ships with newer delphi versions.
I know you are supposed to be able to build x64 apps in Delphi XE2...
I am using a paid version, the starter version.
I checked in options as well and it will not let me change to 64 bit. Only 32.
I am also running XE2 from a 64 bit machine.
Could it be because I have the starter version? If so that is kind of ridiculous, see as I paid over $200 for this software.
Read the Feature Matrix. The 64-bit compiler, OSX compiler, and FireMonkey framework are not available in the Starter edition.
I use FastMM in my Delphi application to trace memory leaking especially in FullDebugMode. With the new release of Delphi XE2, can we use FastMM as the memory manager? Can FastMM work with the Win64 platform?
FastMM is pre-installed in Delphi XE2 and is the default memory manager for both Win32 and Win64 platforms, but the pre-installed version does not include all the features the open-source FastMM (available on SourceForge) provides. To use all of its features (including FullDebugMode), you have to download and install the open source project from SourceForge.
The project on SourceForge is not updated for XE2 yet; that means, for using FullDebugMode you have to wait a few more days until the open source project is updated for XE2 too.
Pierre Le Riche committed changes to the SVN repository yesterday to add support for both 32 and 64 bit targets of XE2.