Forum > Lazarus

Lazarus Release Candidate 1 of 3.0

<< < (35/36) > >>

TRon:

--- Quote from: dbannon on October 18, 2023, 12:35:20 am ---As far as I know, startlazarus is only necessary if you have your install in root space.

--- End quote ---
That is exactly why I asked  :)


--- Quote ---If you install Lazarus into  user space, you can write directory there and its heaps simpler. 'lazarus' is all you need.

--- End quote ---
Yes, I know. fwiw I still prefer to use startlazarus because if Lazarus failed to build correctly then startlazarus will automatically restore the previous working version. At least afaik it is startlazarus that responsible for doing that.

But, that is actually besides the point. sorry for the digression.

Reason to ask is where do the dmg install packages for macos install Lazarus ? My knowledge on that topic is none and I wondered if some of the issues that some macos users report stem from the fact that lazarus is installed to a otherwise protected directory and runs into issue because of not using startlazarus, using the lazarus executable instead.

dbannon:

--- Quote from: TRon on October 18, 2023, 01:27:35 am ---.....
Reason to ask is where do the dmg install packages for macos install Lazarus ? My knowledge on that topic is none and I wondered if some of the issues that some macos users report stem from the fact that lazarus is installed to a otherwise protected directory and runs into issue because of not using startlazarus, using the lazarus executable instead.

--- End quote ---

Don't know, I only ever build Lazarus from source. Especially so on MacOS. But maybe you are right, I'd expect it to end up in a read only directory if installed from a dmg.

Davo

Tomki:

--- Quote from: TRon on October 15, 2023, 09:19:43 am ---
--- Quote from: Tomki on October 15, 2023, 08:41:58 am ---I am unsure about how to install lazarus from source - otherwise I would have tried before. Is there a comprhensive toutorial for that?

--- End quote ---

Provided that you have all dependencies installed and have a working (standalone) and good configured Free Pascal compiler:

- Navigate your browser to https://sourceforge.net/projects/lazarus/files/Lazarus%20Zip%20_%20GZip/
- Select the directory that matches your preferred release of Lazarus
- Download either the zip or tar.gz file
- Extract the archive to a temp location
- then build Lazarus:

--- Code: ---cd <temp location>/Lazarus
make distclean all LCL_PLATFORM=cocoa CPU_TARGET=x86_64 bigide

--- End code ---
Note: Change the LCL_PLATFORM and CPU_TARGET as per your preference/host

- Wait for make to finish.
- Copy the contents of the Lazarus directory to where you wish your Lazarus "to be installed" (that really is the installation and you could even opt to build Lazarus in your 'installation' directory if you so wish to do so)

Use the instructions provided by dbannon to start Lazarus, please don't forget the --pcp option

That is about it for being a comprehensive tutorial.

fwiw probably even less than 2 cents: I agree with dbannon that this does not belong in this thread as there are better places to discuss these kind of things even though you are correct that it is confusing about the availability of different release candidates. Which is even more reason to not discuss RC2 related issues in this RC1 dedicated thread. The issues you mention are usually caused by the convenience of a ready to go installation package (which has to account for all circumstances and therefor not geared towards individual needs/requirements)

btw: (practice and preach, I know  :-[ ) doesn't the Lazarus mac installation package make use of the startlazarus executable ?

--- End quote ---


OK - Done so far. After cleaning up the old installation, I made a fresh install of fpc and fps-source; downloaded the Lazarus ZIP file and unzipped it.
Also, compiling Lazarus with the make worked. According TRons advice I copied everything in the following folder (macOS): "/Users/Thomas/Lazarus"
(However, there is no folder "Configs/")

What I cannot relate to are Davo's instructions
LAZARUS=lazarus-main
open "$HOME/bin/Lazarus/$LAZARUS"/lazarus.app --args "--pcp=$HOME/bin/Lazarus/Configs/$LAZARUS"

I'm sorry, but again, I am just not familiar with these system internals.
Could anyone please tell me how to proceed?
Thanks very much
Thomas

Tomki:
If I open "startlazarus" I get the following error message from Terminal:

Last login: Tue Oct 24 13:03:39 on ttys000
/Users/thomas/Lazarus/startlazarus ; exit;                                     
thomas@Pro-von-Thomas ~ % /Users/thomas/Lazarus/startlazarus ; exit;
Info: (startlazarus) [TLazarusManager.Run] starting /Users/thomas/Lazarus/lazarus.app ...
Info: (startlazarus) [TLazarusManager.Run] exe=/usr/bin/open Params=[-a
/Users/thomas/Lazarus/lazarus.app
--args
--no-splash-screen
--force-new-instance
]
The application /Users/thomas/Lazarus/lazarus.app cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10827 "kLSNoExecutableErr: The executable is missing" UserInfo={_LSLine=3863, _LSFunction=_LSOpenStuffCallLocal}

If I open "lazarus" the IDE starts up, but I have no menu bar at all.  :(

TRon:

--- Quote from: Tomki on October 24, 2023, 01:07:16 pm ---If I open "startlazarus" I get the following error message from Terminal:

--- End quote ---
Can you elaborate on what "open" means in your case ?

According to the wiki it should be:

--- Code: ---open <full_path_required?/>startlazarus.app --args "--pcp=<your unique to this version of Lazarus configuration directory>

--- End code ---
As you can see I do not know or am able to verify some of the details.


--- Quote ---The application /Users/thomas/Lazarus/lazarus.app cannot be opened for an unexpected reason, error=Error Domain=NSOSStatusErrorDomain Code=-10827 "kLSNoExecutableErr: The executable is missing" UserInfo={_LSLine=3863, _LSFunction=_LSOpenStuffCallLocal}

--- End quote ---
Besides the fact that I seem to have missed the --pcp option in the output the above quoted part of the message is more or less clear. Startlazarus seem unable to locate the lazarus.app executable. Again I miss the details / environment to further investigate why exactly that is happening to/for you.

So you happen to have dtruss available on your machine so that you could try and run the open command through dtruss (or perhaps open itself is able to display some detailed output) ? Something like dtruss (I use strace on linux) would allow you to investigate where the command is looking (which directories) to find the files it needs and why the opening of files and libraries fails.

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version