Sign in Join

Live chat for Free Pascal, Lazarus, Delphi and every Pascal programmer.

Mailing lists / lazarus / 2015-09

Testing Lazarus development version easily under Wine

5 messages · 3 people · –

Reply by email Subscribe to this list Your subscription

Read-only archive. Use j and k to move between messages.

Juha Manninen

I don't have Windows right now.
I found out an easy way to test my development repository changes also under Wine.
Lazarus runs amazingly well with Wine.

I installed the latest Lazarus release Windows version on Linux. It opens with Wine automatically, no problems.
Then I ran a bash script (copied below and attached). It deletes the source directories and replaces them with symbolic links to my development sources.
Then I started the Windows version again. It complains about wrong version and a missing package but that is OK.
Then I rebuilt it from Tools -> Configure Build Lazarus ... and I have the latest Windows version of Lazarus running on Linux! Absolutely cool. :)
I can check that my changes don't break the Windows version already before committing them.

Juha

---

#!/bin/bash

# Lazarus development version path.
LazDevelPath=~/SW/lazarus_gitsvn

# Lazarus release Windows version.
cd ~/.wine/drive_c/lazarus

for LazDir in components converter debugger designer doceditor docs examples ide images languages lcl packager test tools do
# Do not delete already linked directories.

  if [[ -L "$LazDir" ]]; then
    echo "Directory $LazDir is already linked"
    continue
  fi
  echo "Linking directory $LazDir to development version"
  # Delete a directory from Windows installation.
  rm -rf $LazDir
  # Replace it with a symbolic link to Linux development version.
  ln -s $LazDevelPath/$LazDir $LazDir

done
-------------- next part --------------
A non-text attachment was scrubbed...
Name: LinkLazFromWineToLinux.sh
Type: application/x-sh
Size: 645 bytes
Desc: not available
URL: <http://lists.lazarus.freepascal.org/pipermail/lazarus/attachments/20150906/b6825422/attachment.sh>

Reply by email

FreeMan
to Juha Manninen

Why did not make symlink to just "LazDevelPath"? just made subfolders?

similar example from me:
My host is osx, linux os (14.04, 14.10, 15.04) on virtualbox. I didn't try use symlink for fpc and lazarus 'cos compiled units be in host (osx) they are trash for osx. I made "shared folder" in virtualbox to osx's "/opt/" folder. In linux, I made symlink for my projects and 2d party components's folders to under linux's "/opt/" folder, then made and build lazarus and test my projects sourse from (host) osx . I made all lpk (-FU) like this:
"../all_libs/lpkname/$(TargetCPU)-$(TargetOS)-$(LCLWidgetType)" my projects's as well. So no conflict.
I wish lazarus have to "environment options" for project and packages output directory

Juha Manninen wrote 44 lines
I don't have Windows right now. I found out an easy way to test my development repository changes also under Wine. Lazarus runs amazingly well with Wine. I installed the latest Lazarus release Windows version on Linux. It opens with Wine automatically, no problems. Then I ran a bash script (copied below and attached). It deletes the source directories and replaces them with symbolic links to my development sources. Then I started the Windows version again. It complains about wrong version and a missing package but that is OK. Then I rebuilt it from Tools -> Configure Build Lazarus ... and I have the latest Windows version of Lazarus running on Linux! Absolutely cool. :) I can check that my changes don't break the Windows version already before committing them. Juha --- #!/bin/bash # Lazarus development version path. LazDevelPath=~/SW/lazarus_gitsvn # Lazarus release Windows version. cd ~/.wine/drive_c/lazarus for LazDir in components converter debugger designer doceditor docs examples ide images languages lcl packager test tools do # Do not delete already linked directories. if [[ -L "$LazDir" ]]; then echo "Directory $LazDir is already linked" continue fi echo "Linking directory $LazDir to development version" # Delete a directory from Windows installation. rm -rf $LazDir # Replace it with a symbolic link to Linux development version. ln -s $LazDevelPath/$LazDir $LazDir done

Reply by email

Juha Manninen
to FreeMan
FreeMan wrote
Why did not make symlink to just "LazDevelPath"? just made subfolders?

Because the standard installation puts FPC into the same folder. I wanted to use the already installed FPC. I could have installed Windows FPC under Wine separately of course but I didn't.

Show quoted text 5 lines
I made all lpk (-FU) like this: "../all_libs/lpkname/$(TargetCPU)-$(TargetOS)-$(LCLWidgetType)" my projects's as well. So no conflict. I wish lazarus have to "environment options" for project and packages output directory

No conflicts here either. The compiled units go automatically to different directories, in this case to i386-win32 and x86_64-linux. I built from the Configure Build Lazarus dialog.

Juha

Reply by email

Marc Weustink
to Juha Manninen: I don't have Windows right now. I found out an easy way to test my development repository…
Juha Manninen wrote
I don't have Windows right now. I found out an easy way to test my development repository changes also under Wine. Lazarus runs amazingly well with Wine.

Good to hear. In the past there was one issue that some type of bitmaps were shown upside down. If you see a normal looking lazarus toolbar, then I think the issue is solved.

Marc

Reply by email

Juha Manninen
to Marc Weustink
Marc Weustink wrote
Good to hear. In the past there was one issue that some type of bitmaps were shown upside down. If you see a normal looking lazarus toolbar, then I think the issue is solved.

Yes, it is fixed.
I have now Manjaro Linux which has the latest versions of everything. Wine is 1.7.51-1.

Juha

Reply by email