How to port a package to OAH build?

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

I spent some days on OAH, and got some knowledge, I'm writing down them here in case it helps others.
OAH build contains a series custom build rules to process gtk+ build tasks:
DoIn Generate Tool for "*.in" files;
Pkg-Config Tool to run "pkg-config" command to get the build dependencies
GObject marshal generator to run "glib-marshal"
GObject Enum generator
Header File Installation Tool to copy the header files into the proper directories.

Basic steps:
1. create a directory hierarchy $(top_srcdir)/win32/oah
2. create a new solution and a new empty project for your package (this will create a directory named after your project to hold the project files, which doesn't conform to the other oah directory structures, so you gotta move them out and change the solution file)
3. right click on the project and choose "Custom build rules", then "OAH build tools"
4. right click on the project and choose "properties"
   4.1 Configurations->General,
  Inherited Project Property Sheets": put in "$(OAH_INSTALLED_PATH)\vsprops\oah-$(PlatformName)-$(ConfigurationName).vsprops;
$(OAH_INSTALLED_PATH)\vsprops\oah-PC.vsprops" and your own inherited project sheets, if there are any.
   4.2 DoInGenerator tools: the *.in files should be added to resource file list, put in your substitutions.
   4.3 Pkg-Config Tool: pkg-config dependencies, there are two ways to specify pkg-config dependencies: put in a separate file with a file extension "oahdeps", or as the parameter of additional dependencies
   ...
5. add source files
6. add resource files, such as *.in, *.oahdeps

7. build and tweak

Good sum up by Shixin!

Some additional information:
When editing properties in step 4; You should first select All Configurations and all platforms, since most of what you are changing will be similar for all configuration (Debug, Release) on all platforms (Win32, x64).

oah-PC.vsprops usage:
When using this property sheet, you must manually open your .vcproj file and edit RootNamespace. RootNamespace must be identical to the name of either the .oahdeps or .pc, depending on whats being used.

Thanks for your tips.

Another question regarding to Pkg-Config Tool, if I only specify the dependency as the parameter to "additional dependencies" and not provide *.oahdeps, it seems that pkg-config doesn't run at all. Any idea?

Yes, you are correct! Visual Studio or VCBuild is built around input files and output files, so yes, until we find a way to create a custom build tool that does not depend on an input file, you will need to add an empty .oahdeps file to your project.