Old versions of fpc need winff.res file in source package

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Download source package
2. Try to compile

What is the expected output? What do you see instead? Successful compilation, 
errors for lack of said file arise.

What version of the product are you using? On what operating system? 1.42

Please provide any additional information below.

I fixed this problem by getting the winff.res file from trunk, still, it should 
be supplied along with the package.

Original issue reported on code.google.com by y...@julianbayardo.com.ar on 28 Mar 2012 at 4:39

[GoogleCodeExporter]

Hmm, very interesting. As this winff.res file is generated I removed it from 
the tar ball and from the repository. Where did you find it? I don't see it in 
trunk. Anyway. How do you compile Winff, as for me, both compiling it in the 
Lazarus IDE as command line, it builds fine without the winff.res file in the 
tar ball.

If you found a winff.res file somewhere it is probably completely outdated. I 
am not sure if it matters thou.

Please state the OS you are using and which version of fpc and lazarus you have.

Original comment by poipodec...@hotmail.com on 28 Mar 2012 at 8:06

• Changed state: Incomplete

[GoogleCodeExporter]

Sorry I took this long, I planned to include that information in the first 
post, but time was lacking and that was the best way not to forget to report 
it. I'm running Linux (Gentoo), x86_64, with kernel 3.3.0, preempt with smp. 
I'm using FPC 2.4.0 for x86_64, along with Lazarus 0.9.28.2 beta, svn revision 
is 638.

Said revision contains a winff.res in the winff1.5 folder within the root 
directory (by the way, there's a weird directory named " winff --username 
bggmtt", I believe this is probably a mistake as well, as it seems to be an 
exact copy to the winff1.5 folder). Now, I've updated a previous ebuild for 
portage so as for it to install WinFF 1.4.2, said ebuild downloads your sources 
package ( https://winff.googlecode.com/files/winff-1.4.2-source.tar.gz ), 
decompresses it, and compiles it using this command: "lazbuild --widgetset=gtk2 
-B winff.lpr || die". Using your default sources, the output is as logged. 
Copying the winff.res from the svn revision works as expected and produces a 
perfectly usable executable.

Attached files:

lazarus.log -- failure log from Lazarus.
succesful.log -- full success.

Original comment by y...@julianbayardo.com.ar on 29 Mar 2012 at 12:59

Attachments:

• succesful.log
• lazarus.log

[GoogleCodeExporter]

It seems related to your version of FPC and Lazarus, as newer seem to work 
without problems. I had the same problem before on an older system as can be 
seen here at [1].

The winff1.5 tree should be disregarded as it has never been used for 
development, the " winff --username bggmtt" is the real source of our project 
with the winff-1.4 branch being the source of our current 1.4.2 tar ball. I 
agree with you that the name could be have been chosen better, but I as a 
rename on an other svn project of mine has introduced quite some annoyance with 
the users, I am hesitant to propose a rename here.
[1] 
https://launchpadlibrarian.net/95052676/buildlog_ubuntu-lucid-amd64.winff_1.4.2-
2~ppa1l_FAILEDTOBUILD.txt.gz

Original comment by poipodec...@hotmail.com on 29 Mar 2012 at 6:45

• Changed title: Old versions of fpc need winff.res file in source package
• Changed state: Accepted

[GoogleCodeExporter]

I'll try to upgrade Lazarus and FPC. Is there any way to actually fetch and/or 
compile that .res file myself so I could make a proper ebuild for this project 
and ask for addition to the portage tree, there seems to be a plenty of people 
looking out for this program.

Other than that, I believe you should rename the tree, it is very much 
confusing and bothersome.

Original comment by y...@julianbayardo.com.ar on 30 Mar 2012 at 2:38

[GoogleCodeExporter]

I don't know how to make a winff.res file, but with a newer lazarus, it will 
automatically create one if you compile the project. No need to do anything 
special. I think you could use the one from the winff1.5 tree, or I could send 
you one if you need it before you can upgrade. But I don't think you need one 
after the upgrade.

On the tree rename: I put the question to the other developers. We'll see what 
they think.

Original comment by poipodec...@hotmail.com on 30 Mar 2012 at 7:37

[GoogleCodeExporter]

Nice. Also, could you tell me which version of fpc - lazarus you're using?

Original comment by y...@julianbayardo.com.ar on 30 Mar 2012 at 7:43

[GoogleCodeExporter]

FPC: 2.4.4 (Debian distribution, version 3.1): 2.4.4-3.1 [2012/01/04] for i386
Lazarus: 0.9.30.2 (Debian distribution, version 2) 

Original comment by poipodec...@hotmail.com on 31 Mar 2012 at 9:55

[GoogleCodeExporter]

I decided to close this bug. I don't want to provide such automatically 
generated files in the tar ball. If people are still using the old lazarus and 
command line to build, they can get the file in the svn repository.

http://winff.googlecode.com/svn-history/r641/trunk/winff1.5/winff.res

Original comment by poipodec...@hotmail.com on 1 Aug 2012 at 6:44

• Changed state: WontFix
• Added labels: Type-Other
• Removed labels: Type-Defect