Dumb question for you after looking at changes / fixes, what is cocoa ?macOS API
(Actually "Privativa" in Spanish, don't know how's in English).
Not true. It is GPL licensed. Some file must be missing or wrong for Software to report it as Proprietary.Actually:
./postinstall: /tmp/PKInstallSandbox.vFZ5uH/Scripts/org.freepascal.pkg.fpc-macos-x86-64-laz.QajxE2/postinstall: line 8: /usr/local/lib/fpc/Error: ppcx64 can't be executed, error message: Failed to execute "ppcx64", error code: 127/samplecfg: No such file or directory
I was going to install lazarus-project_2.0.8-0_amd64.deb on my Xubuntu and I've seen that Software (the application that installs it) says the license is private (Actually "Privativa" in Spanish, don't know how's in English).Thats because you are looking at it using the Gnome supplied 'Software' or 'Software Install' tool. It classes anything that does not come from its own repository as proprietary. I have seen numerous bug reports on the topic, they just seem to be ignored and, quietly closed. I suggest you install gdebi and use that instead.
Privativa = Proprietary (non-free)Thanks. I forgot it. :)
Thats because you are looking at it using the Gnome supplied 'Software' or 'Software Install' tool. It classes anything that does not come from its own repository as proprietary. I have seen numerous bug reports on the topic, they just seem to be ignored and, quietly closed. I suggest you install gdebi and use that instead.Thanks for the explanation. I'll try Gdebi. :)
As an experiment, grab a deb from your /var/cache/apt/archive/*, to be really nasty, see if you can find gnome-software..... It most certainly came from the approved repository and is open source. Open it with Software-Install and you will see it claims it, itself, is proprietary !
Any file that is not in the official repository is reported as proprietary. Even if it came from the repo.
I believe newer distros have stopped that particular tool from claiming its a general software management tool. Gdebi is your friend.
Davo
There are also snapshot builds for anyone who wants to test with fpc 3.2 RC/fixes: https://sourceforge.net/projects/lazarus-snapshots/files/
The "/Window 64/2020-04 l..beta-44680-win64.exe" file could not be found or is not available. Please select another file
Can you try again please?
The Lazarus team is glad to announce the release of Lazarus 2.0.8.
This release was built with FPC 3.0.4.
That's normal behavior...
Nothing has changed there.
its just a method in the class with code in it. Delete it.
But it's referencing a component that no longer exists on the form. This always used to come up with the warning and ask if you want to remove the associated declarations.No, its not.
I was going to install lazarus-project_2.0.8-0_amd64.deb on my Xubuntu and I've seen that Software (the application that installs it) says the license is private (Actually "Privativa" in Spanish, don't know how's in English).
As I noted in my post above, if you look at a package in the Software Installer in the normal manner where the package is located in their repository, most (all ?) will not be Proprietary. Manually download one to your local disk, then look at it with Software Install and it has magically become Proprietary. Its not the content of the package that matters, any package that exists anywhere other than in their repository is Proprietary.
It's "Proprietary" in English.
.....
But the software center still shows "Proprietary".
I tried the simplest license "GPL-2", but Software Center still shows "Proprietary".
I could not rebuild the 32 bit version on W10 got "Fatal:(1009) No memory leftNormally this is a well known problem of the used (32-Bit) FPC version. You can look for it in the Forum search.
I am downloading the win32 version from:Yes it is.
https://sourceforge.net/projects/lazarus/files/Lazarus%20Windows%2032%20bits/Lazarus%202.0.8/lazarus-2.0.8-fpc-3.0.4-win32.exe/download
Isn't this the official Windows 32 bit version?
Thanks for the answer @Martin_fr. I asked this question, because I remember a few days ago reading somewhere that a Win32 version for 2.0.8 will not be released and the users will need to build it themselves.Indeed, IIRC that was about 3 or 4 weeks back.
On W7 installed the 64 bit version and cross compiler, just have to change the settings to 32 bit target.
So far it runs without problems, thanks all :)
Yes I know the build mode but have not used them yet.
fpc 3.2.0 beta gives in a small test program many lines like "Note: Call to subroutine "operator +(const op1:Variant;const op2:Variant):Variant;" marked as inline is not inlined"
I could disable the messages but I think I will use laz 2.0.8 fpc 3.0.4 64->32 that runs as expected.
Yes I know the build mode but have not used them yet.
fpc 3.2.0 beta gives in a small test program many lines like "Note: Call to subroutine "operator +(const op1:Variant;const op2:Variant):Variant;" marked as inline is not inlined"
I could disable the messages but I think I will use laz 2.0.8 fpc 3.0.4 64->32 that runs as expected.
Afaik 3.0.4 does not inline it either. It just does not tell you that it did not.
I could not find a enable/disable in the compiler options, messages, [...]
Perhaps I could be trying to understand or provide you with more relevant information.
The zarus makes me the errors put in image.Probably open a new thread.
Do you know if this is the case where the conf files are located which allow lazarus to find these little ones in this tree. Perhaps I could be trying to understand or provide you with more relevant information.Not sure what you mean. (Maybe lost in google translate?).
Vous avez raison, je vais éviter Google translation. Je pose mes questions en Français et ceux qui ont la gentillesse d'y répondre traduiront avec les outils de leur choix.Best to do both. Translated and original.
I installed :
fpc-3.0.4-macos-x86_64-laz-2.pkg
fpc-src-3.0.4-laz.pkg
and LazarusIDE-2.0.8-macos-x86_64.pkg
PATH=/usr/bin:/bin:/usr/sbin:/sbin
Lazarus is started by the application folder where the Lazarus icon is installed.
The described problem also occurred on macOS Mojave. A new installation with the latest versions was successful.
@trev, mattias:
The described problem also occurred on macOS Mojave.
A new installation with the latest versions was successful. One small note: The FPC sources are now in /usr/local/share/fpcsrc/3.0.4; you have to adjust this at IDE-startup This is new.
jeanhunter@MacAlliance / % sudo xcode-select --install
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
Ca donne çà : (It gives that :)
jeanhunter@MacAlliance / % sudo xcode-select --install
Password:
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
jeanhunter@MacAlliance / % sudo xcodebuild -license accept
jeanhunter@MacAlliance / %
Bon, la catastrophe pour rien. Installation d'une version vierge de Catalina, puis installation dans l'ordre de :
fpc-3.0.4-macos-x86_64-laz-2.pkg
fpc-src-3.0.4-laz.pkg
LazarusIDE-2.0.8-macos-x86_64.pkg
Compilation Lazarus profil normal Cocoa -- Darwin -- x86_64
Résultat :
BonjourBien que certains d'entre nous puissent communiquer en français, nous ne devrions pas le faire ici.
Dans le fichier fpc.cfg, je n'ai :
ni -->-Fl/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib/
ni --> #ifdef cpux86_64
J'ai fait l'installation de Lazarus sur une machine Catalina vierge. Ce n'est pas une mise à jour, mais un disque complètement réinstaller.
Best to do both. Translated and original.
(Includes les Francais avec les translation)
Il suffit de faire un click droit sur le bord gauche de la page pour que google fasse une traduction automatique. Quand vous écrivez en Anglais, c'est ce que je fais. La politesse doit être réciproque.Some strange logic there.
My google chrome translates everything automatically and relatively correctly. So without wanting to argue it is an archaic mode of operation. I think the user of Lazarus from other countries would find more interest in finding articles in various languages.
Je sens que les trolls sont de sortie et pas un seul d'entre eux ne m'aidera à résoudre pour moi et pour tous les problème de Lazarus sur Catalina.if I could help you with Catalina related problems, at least I would try, in English, of course!.
Je rappelle aux Trolls que l'Anglais n'est parler que par 400 ou 500 million d'individus pour 7 milliard d'humains.Not only you expect people to accommodate your preference for French (the preference is understandable, your expecting other people to accommodate it... not so much) but you provide incorrect information to support your unfounded expectations. I can't help you with the Catalina problem but, I can help update your knowledge of how many people speak English and how many speak French. Obviously, the figures are estimates but, they are along these lines: 1.5 to 2 BILLION (that's millard in French - see... very kind and accomodating) people speak English and the majority of them speak it as a second language. There are about 270 MILLION (same in French) people who speak French (and that number includes people who _believe_ they speak French (e.g Cajun) which is not the same as actually speaking French.)
merciDe rien. You're welcome.
Thanks
Merci beaucoup.
J'ai donc remplacer le fpc.cfg dans le répertoire et Lazarus démarre. Il accepte de compiler un exemple de programme qui se compile très bien et marche normalement avec la version Windows. J'ai installé la version windows sous windows 7 dans une machine Parallel Desktop.
La version windows marche normalement, la version Mac ne marche pas, pas d'accès au fichier comme sur la vue d'écran.
Donc suite à cela je recompile Lazarus et la problème Id Warning: building for mac os 10.5 deprecated
Je persiste car je pense que cela peut servir à la communauté.
Hello, I've noticed an issue with TListview multiple selection on Windows, with Lazarus 2.0.8.The issue will be fixed in 2.2
To replicate the issue: create an empty application, place a TListview on the form and populate it with a few test items, check Multiselect true for the TListview.
Mr Trev n'a rien compris. J'ai écrit que le programme exemple se compilait bien sur Lazarus WINDOWS. Mais je m'en fout, je veux utiliser la version MAC Catalina.Merci beaucoup.
J'ai donc remplacer le fpc.cfg dans le répertoire et Lazarus démarre. Il accepte de compiler un exemple de programme qui se compile très bien et marche normalement avec la version Windows. J'ai installé la version windows sous windows 7 dans une machine Parallel Desktop.
La version windows marche normalement, la version Mac ne marche pas, pas d'accès au fichier comme sur la vue d'écran.
Donc suite à cela je recompile Lazarus et la problème Id Warning: building for mac os 10.5 deprecated
Je persiste car je pense que cela peut servir à la communauté.
As I have fixed your initial problem, PLEASE start a new thread in an appropriate forum.
[...]
- The examples appearing in Lazarus cannot be compiled, because that obliges to create a directory in the folder of the example which is in \ Lazarus 2.0.8 \ bibliotheque \ Lazarus \ examples which is a directory prohibited by Catalina in writing .
Do you want to explain to me how to do it and I agree to do the guinea pig.1) Install macport according to their homepage (https://www.macports.org/install.php)
For information, I installed it on a Windows 7 virtual machine and this version works.
...... An attempt by the Trolls to impose English?)
.......nice and compassionate people, which is not the case for Mr Trev.
Did you install the packages in that order? (ie 1, 2, 3 as listed above)
Which problem?
Maybe this is related to installations where you already have a copy installed? For new installations on a "clean system" (ie newly installed operating system) I've not had to change anything for it to work.
I have attached a correct fpc.cfg from a new FPC install on Catilina. Copy the fpc.txt file to /etc/fpc.cfg
As I have fixed your initial problem, PLEASE start a new thread in an appropriate forum.
Quel problème?
Peut-être que cela est lié aux installations où vous avez déjà installé une copie? Pour les nouvelles installations sur un "système propre" (c'est-à-dire un système d'exploitation nouvellement installé), je n'ai rien eu à changer pour que cela fonctionne.
What problem?
Maybe this is related to installations where you have already installed a copy? For new installations on a "clean system" (that is, a newly installed operating system), I didn't have to change anything to make it work.
When I speak of troll, it is in reference to the fanatics who want to impose the exclusive English language.That rings a bell but, the last one of those fanatics I saw was trying to impose french in the English section of the forum. Imposing English in the English section of the forum... what a "strange" thing to do... it's obvious everyone should post in french in the English section.
Lucamar:For now I will use the default Lazarus with fpc 3.0.4
To do that you can either insert a {$WARN number OFF} directive in your code or use fpc's option -vm<x>. You can find them in FPC's Programer's Guide and apendix A of the Users Guide respectively.
QuoteTo do that you can either insert a {$WARN number OFF} directive in your code or use fpc's option -vm<x>. You can find them in FPC's Programer's Guide and apendix A of the Users Guide respectively.For now I will use the default Lazarus with fpc 3.0.4
I wish I had time to play more with fpc 3.2.0 beta, well, some day :)
The mildly confusing - the DateTimePicker component requires the DateTimePicker unit to be explicitly added to your project - this isn't related to 2.0.8, it happened in 2.0.6 too.In trunk this works. If it really was fixed recently it should have been merged to 2.0.8. Anyway it will work in future 2.2.0.
I just installed Laz 2.0.8 for Win64, the DateTimePicker is installed by default. I cannot imagine that mac OS should be different here.
The slightly less good - I had to adjust all my strToDate methods to include the separator. Previously StrToDate('2020-05-01) worked, now it needs to be StrToDate('2020-05-01','-'). Not a big problem really.Maybe locale settings?
The mildly confusing - the DateTimePicker component requires the DateTimePicker unit to be explicitly added to your project - this isn't related to 2.0.8, it happened in 2.0.6 too. While this isn't a big deal it may confuse some as it's completely at variance with all the other components on the palette.Could be various things.
Now I get an "EOutOfResources" - no timers available - error when the previously running app programmatically creates a timer (Well - actually when it sets Event handlers - not when creating the timer).I don't see an error in this piece of code. Need more info.
Happens in FormCreate - and no, it's not in any loop.Call stack sets error at the line where OnTimer eventhandler is set.
That is here :@matthius, please create a new thread instead of replying and then changing the subject line.
https://sourceforge.net/projects/extpascal-restore/files/ (https://sourceforge.net/projects/extpascal-restore/files/)