| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
update Localizable.strings to ensure it is always up to date. This addresses the second point of issue #593. Also, add a bunch of status messages to the script to provide feedback on the current operation.
|
|
|
|
|
|
|
| |
previous 5.1.36
- Update MySQL client build script for snow leopard compatibility, and to build the client libraries as a three-way binary (x86/ppc/x86_64) in keeping with the rest of Sequel Pro
|
| |
|
|
|
|
|
|
|
| |
(thanks to Stuart!)
- Improve debug code signing by also signing the tunnel assistant, and add code signing for Distribution builds. This addresses Issue #426. (assistant signing improvement also applied to nightlies)
|
|
|
|
| |
make it easier to work with.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Includes all custom code from subclasses CMMCPConnection and CMMCPResult, meaning they have subsequently been removed from the project.
- All previous Sequel Pro specific code in the above subclasses has been removed in favour of the delegate (currently set to TableDocumet) informing the framework of such information.
- All references to CMMCPConnection and CMMCPResult have subsequently been changed to MCPConnection and MCPResult.
- Framework includes MySQL 5.1.36 client libraries and source headers.
- Framework is now built as a 4-way (32/64 bit, i386/PPC arch) binary.
- All import references to <MCPKit_bundled/MCPKit_bundled.h> have been changed to <MCPKit/MCPKit.h>.
- New script 'build-mysql-client.sh' can be used to build the MySQL client libraries from the MySQL source. See the script's header for a list of available options or run it with no arguments to display it's usage.
Note that there are still a few changes to be made to the framework with regard to removing Sequel Pro specific calls to the delegate. These however can be made later on as they have no effect on functionality and are merely design changes.
Also, note that any future development done on the framework should be made to be as 'generic' as possible, with no Sequel Pro specific references. This should allow the framework to be integrated into another project without the need for SP specific code.
|
| |
|
|
|
|
| |
and ~10% smaller distribution file
|
|
|
|
|
|
|
|
| |
soon as the new framework is used (ie before 0.9.6)
- Add a public key to the project and add a link to it in Info.plist for use by Sparkle when verifying future updates
- Add a new build configuration (Distribution), and add a new script for use with only that configuration - constructs a basic disk image, asks for the private key file, and signs it.
|
| |
|
| |
|
|
|
|
| |
whole meg on current build.
|
|
|