Original build files

[ZanderBrown]

On Wine 3.4 the status bar doesn't seem to be rendered

Any chance we could have the original Makefiles as well as the VS solution?

I'm unable to build from a .sln and #9 will be challenging without Makefiles as well

[badsectoracula]

Shouldn't this be filed against Wine? After all it is supposed to be bug-for-bug compatible, this is an example where it isn't the case and the developers can check the source code of WinFile to see why. I think it is better to file this against the Wine developers so that they can make their implementation behave like Windows does than alter WinFile to make it work better with Wine.

[ZanderBrown]

Sure, point still remains about Makefiles though

[craigwi]

Regarding the makefiles, the project originally used a Microsoft internal build system. The primary file in the project used to describe building WinFile.exe was called 'sources'. That file contained the same information now in the vcxproj. The original 'sources' file is attached (renamed to .txt for upload).

sources.txt

[sskras]

It would be nice to have the issue renamed then:)

[ZanderBrown]

Without knowing this internal build system it looks like Autotools style macros for generating a Makefile

Might get vc++ out and make them 'real'

[ghost]

The internal build system is known as Razzle. Razzle uses a makefile.def Nmakefile in \public\oak\ which is included from the source level makefile (in this case .\makefile), that includes .\sources (which to clairify, sources is simply a Nmakefile with no targets, and sources is included from makefile.def), which then compiles/links source code from variables in .\sources into a executable using the rules inside of makefile.def.

You can actually see bits of razzle in the Windows DDKs (which, really are just razzle without developer profile and source control support, as well as not shipping with library and operating system source code), especially older ones like NT4-Srv03.

Nonethenless you should be able to use a DDK with a modified (or not if DDKs expose privapi) sources file and a makefile that includes makefile.def (protip, you can just use includemakefiles from the DDK samples since all they do is include makefile.def)

[ZanderBrown]

Roughly what I thought was happening