Hi, all.
Over the weekend, I noticed a big flaw in Buildtool. The property aliasing, such as: path="{$gtk}/lib"
...was done at file-read-time. This made it impossible for a Task to use the results of another task as input. So all of the Tasks were recoded to have late binding.
Package-config now works. To query a package, just use
${pc.packageName} for the 'all' query, ${pcc.packageName} for the 'cflags' query, and ${pcl.packageName} for the 'libs' query.
Note that this is processed internally, and does not call the pkg-config executable. It also grabs all dependent packages' queries, too.
This is in addition to the existing: ${env.VARIABLE_NAME} to fetch an environment variable.
I did a test build, and it seems to work ok. Please let me know if there are any problems. After you svn up, you will need to do:
g++ buildtool.cpp -o btool.exe
...again, for btool to use build.xml properly.
bob (ishmal)
Hello.
On Mon, May 12, 2008 at 1:26 PM, Bob Jamison <rwjj@...127...> wrote:
[...] So all of the Tasks were recoded to have late binding.
Package-config now works. To query a package, just use
${pc.packageName} for the 'all' query, ${pcc.packageName} for the 'cflags' query, and ${pcl.packageName} for the 'libs' query.
Note that this is processed internally, and does not call the pkg-config executable. It also grabs all dependent packages' queries, too.
You, sir, rock.
Daniel Díaz yosoy@...31...
This is in addition to the existing: ${env.VARIABLE_NAME} to fetch an environment variable.
I did a test build, and it seems to work ok. Please let me know if there are any problems. After you svn up, you will need to do:
g++ buildtool.cpp -o btool.exe
...again, for btool to use build.xml properly.
bob (ishmal)
participants (2)
-
Bob Jamison
-
Daniel Díaz