Since the PM merge we now have way too many targets,
here jam clean just fails in execve() due to too long arguments.
jam clean is now very verbose but at least it works.
Another option could be to override the Clean rule itself
to clean in batch by splitting the list...
Patches welcome.
* The new class is called DriverSettingsMessageAdapter which can translate
between a driver_settings file, and a BMessage.
* The net_server Settings class is now just using this class.
jam fails in execve() trying to run the command due to
a too large arguments list because of the many objects in libgcc.
We split them into two intermediate objects,
then we link them to libroot.
- gcc2 lacks the -iquote option, and side effects of some of the other flags
we use with it during the build cause some of libcurl's includes to fail.
This temporarily works around the problem until gcc2 can be suitably fixed.
- PackageManager: Add simple progress listener class for other parts
of depot to use, which in turn is notified when the user interaction
handler's download progress hook is called.
- InstallAction: Implement progress listener interface and add self
as listener when initiating a package installation.
This gets basic download progress reporting working in Depot, but isn't
yet complete, as, with the current implementation it doesn't properly handle
any dependent packages that might get downloaded, since InstallAction currently
only knows about the package info that it's directly responsible for. Needs a
bit more work to handle that correctly.
- Add accessors for storing/retrieving current download progress.
- Adjust PackageListView to be able to create a progress state from
the download percentage.
- BJobStateListener: Add progress state and corresponding hook.
- FetchFileJob: Notify job progress hook on libcurl notifications.
- UserInteractionHandler: Add hooks for download progress and checksum
validation progress.
- PackageManager: inherit from JobStateListener and watch for job
notifications for internally generated jobs. Forward to corresponding
UserInteractionHandler hooks as needed.
- Adapt pkgman, HaikuDepot and package_daemon to above changes.
Neither HaikuDepot nor package_daemon's progress hooks are wired up to
do anything yet though.
- Pull functionality back into package manager itself since the extra
indirection doesn't really buy us anything in this case, as neither
request that it handles requires a decision provider.
- Adjust pkgman and HaikuDepot accordingly.
- A subset of jobs that require a BContext don't in fact make use of the
decision provider. As such, make the default implementation usable for
those cases so one doesn't need to always create a dummy derived class.
* This has positive and negitive effects. Using the
first monitor's EDID vs the VESA EDID means DisplayPort
monitors and adaptors function. I think the benefits
outweigh the risks at this point.
* Haiku will use the native display mode of the first
monitor and set it across all attached displays.
* Please open bug reports if you notice and regressions.
* List library dependencies.
* Remove "Specific: Linux" section. I can only assume that zlib1g-dev
is/was a package for a specific distribution.
* "Configuring your build" section:
- Mention that a change of the cross-compilation tools may require
re-configuring.
- Update the configure calls as required since the package management
merge.
* "Building via Jam" section:
- Use build profiles.
- Consequently use "-q".
François Revol