I have no clue. Resources are implemented in a platform independent way now, so I can't see why they are not supported on Amiga and the likes. Is that the official source? Are you using 3.0.0 or trunk as FPC?
...and have error "forms.pp(1794,2) Error: Resource files are not supported for this target"How i can fix that?
How i can see revision of fpcres?
Yes every project with lcl has this problem
Target morphOS
Which lcl widget type have you selected for your project ? Which resource comiler settings ? still there is the question of pointing lazarus to the correct FPC 3.0 directory which contains the necessary cross-compiler.BTW: Every project ? even if you compile for your native OS ?
Given that fpc 3.0.0 release was tagged at revision 32319 t is of no concern.
With regards to cross compiling for MorphOS:- Have a good and in working order Free Pascal 3.0.0 compiler- Download the Free Pascal sources from svn (or download a daily zip)- Create a Free Pascal 3.1.x compiler and cross-compiler from those sources you just obtained- Download Lazarus from ALB42's github account. Make sure to select the MorphOS branch (and not the default AROS branch) and build that branch.- Start Lazarus. As Molly suggested: use the extra configuration option in case you have another Lazarus installed.- Make sure Lazarus uses your freshly compiled Free Pascal 3.1.x compiler- Create a new project- Make sure to select mui as widgetset, set the processor to PowerPC and the target to MorphOS- Build your projectThat should do the trick.
I do all excluding Make sure to select mui as widgets. How i can do it on mac?
- Download Lazarus from ALB42's github account. Make sure to select the MorphOS branch (and not the default AROS branch) and build that branch.
Wouldn't be better to add this to the official Lazarus repository? It's a little inconvenient to have multiple lazarus sources on Harddisk.
yes! It will be better, but on this lazarus is not work win32 crosscompile
In software engineering, a project fork happens when developers take a copy of source code from one software package and start independent development on it, creating a distinct and separate piece of software.
Distributed revision control (DVCS) tools have popularised a less emotive use of the term "fork", blurring the distinction with "branch".[15] With a DVCS such as Mercurial or Git, the normal way to contribute to a project is to first branch the repository, and later seek to have your changes integrated with the main repository.
This branch is 188 commits ahead, 2762 commits behind graemeg:upstream.
This branch is 157 commits ahead, 2762 commits behind graemeg:upstream.