I was trying to look at the OGR api in GDAL, and was following the tutorial here: http://www.gdal.org/ogr_apitut.html. I kept getting an undefined reference to pretty much everything. I've installed from source the latest version (1.11) on my linux distro from here: http://trac.osgeo.org/gdal/wiki/DownloadSource. Looking through the header file, specifically in gcore/gdal.h, I see for example that GDALOpenEx is not there, nor is it in the version before that. It is, however, in the subversion repository. So, what gives?
There is no GDALOpenEx function for GDAL 1.11. You are looking at documentation for GDAL 2.x.
The documentation for 1.11 is found at http://gdal.org/1.11/
Or, you can make the documentation for the version you are using locally, e.g.:
make docs
sudo make install-docs
Then view them locally from your web browser, e.g.:
chromium /usr/local/doc/ogr/ogr_apitut.html
Related
I need to deploy and launch 2sxc module source code locally on my pc. Which release version is stable and has correct references? I tried it with version 11.05.00, but didn't succeed so far.
What problems did you find, and which version of DNN are you using?
I have 2sxc 11.4.0 running in a DNN 9.7.2 installation. No problems.
Looking at GitHub, I see 11.07.01 for LTS and a couple of "minor bugfix" releases following it. It looks like I should consider updating ...
Basically almost all releases are stable - and we recommend LTS releases.
I don't understand what you mean with correct references - could you elaborate?
When I try installing with command line:
composer self-update && composer create-project --prefer-dist cakephp/app my_app_name
I keep getting this message, which I didnt use to have, now which one is required, which one is not, do I have to download manually everytime?
cakephp/app suggests installing markstory/asset_compress (An asset compression plugin which provides file concatenation and a flexible filter system for preprocessing and minification.)
cakephp/app suggests installing dereuromark/cakephp-ide-helper (After baking your code, this keeps your annotations in sync with the code evolving from there on for maximum IDE and PHPStan compatibility.)
cakephp/app suggests installing phpunit/phpunit (Allows automated tests to be run without system-wide install.)
cakephp/cakephp suggests installing lib-ICU (The intl PHP library, to use Text::transliterate() or Text::slug())
symfony/console suggests installing symfony/event-dispatcher ()
symfony/console suggests installing symfony/lock ()
symfony/console suggests installing psr/log-implementation (For using the console logger)
m1/env suggests installing m1/vars (For loading of configs)
asm89/twig-cache-extension suggests installing psr/cache-implementation (To make use of PSR-6 cache implementation via PsrCacheAdapter.)
aptoma/twig-markdown suggests installing michelf/php-markdown (Original Markdown engine with MarkdownExtra.)
aptoma/twig-markdown suggests installing knplabs/github-api (Needed for using GitHub's Markdown engine provided through their API.)
ajgl/breakpoint-twig-extension suggests installing ext-xdebug (The Xdebug extension is required for the breakpoint to work)
ajgl/breakpoint-twig-extension suggests installing symfony/framework-bundle (The framework bundle to integrate the extension into Symfony)
ajgl/breakpoint-twig-extension suggests installing symfony/twig-bundle (The twig bundle to integrate the extension into Symfony)
psy/psysh suggests installing ext-pcntl (Enabling the PCNTL extension makes PsySH a lot happier :))
psy/psysh suggests installing ext-posix (If you have PCNTL, you'll want the POSIX extension as well.)
psy/psysh suggests installing ext-pdo-sqlite (The doc command requires SQLite to work.)
psy/psysh suggests installing hoa/console (A pure PHP readline implementation. You'll want this if your PHP install doesn't already support readline or libedit.)
These are only suggestions that may extend the functionality of already installed packages, but everything should work fine without them. For example monolog/monolog will suggest a couple of plugins that will allow logging into different backends. But monolog/monolog will work without them - you may not be able to log for example to Sentry, but monolog will still be usable without this feature.
So usually you can just ignore these suggestions. But you can take a few minutes to check what these suggested packages are actually doing - you can learn about new technologies and solutions that can make your app better and easier to maintain.
If you're really not interested in these suggestions, you can use --no-suggest switch to avoid displaying them on install/update/require:
composer install --no-suggest
According to the official list of built-in libraries, ujson is available. However, the following app.yaml snippet:
libraries:
- name: ujson
version: '1.35'
...generates this error:
Usage: appcfg.py [options] update <directory> | [file, ...]
appcfg.py: error: Error parsing ./app.yaml: the library "ujson" is not supported
in "./app.yaml", line 89, column 1.
If I try to use other supported C libraries like numpy, it works fine. I am running SDK 159.0.0 (latest) and can even see a "ujson" entry in google-cloud-sdk/lib/googlecloudsdk/third_party/appengine/api/appinfo.py.
Any clue why ujson isn't usable?
ujson v1.35 was added to the app engine runtime in Python SDK version 1.9.55.
This sdk version wasn't included in the gcloud sdk until v161.0.0 (2017-06-28):
Updated App Engine components for Python to version 1.9.55. Please visit the release notes for details
Anecdote:
Some of us still prefer appcfg.py update . instead of gcloud app deploy app.yaml.(We are a rare and dying breed :D).
So in the past I noticed that the appcfg.py tool I was using was an older version from the older app engine tooling. Doesn't come with all the gcloud components update awesomeness. You had to download the binaries each time.
which appcfg.py should reveal the exact one being used which for me was:
$ ~/google_appengine/appcfg.py
I can't say I wasn't warned enough. Besides, I kept seeing this advice/warning each time I ran gcloud components update:
WARNING: There are older versions of Google Cloud Platform tools on your system PATH.
Please remove the following to avoid accidentally invoking these old tools:
/Users/jeff/google_appengine/endpointscfg.py
/usr/local/bin/endpointscfg.py
/Users/jeff/google_appengine/dev_appserver.py
So update to the latest version, update your paths to point to the right appcfg, and enjoy ujson or any of the goodies as and when they drop.
$ ~/google-cloud-sdk/platform/google_appengine/appcfg.py update .
Just learning atk4. (4.2.4, I believe. Installed through curl -sS http://agiletoolkit.org/install | sh)
How do I modify and load shared.html in atk4? I can only edit atk4/templates/shared/shared.html?
I tried copying shared.html to the following locations and edit them:
/templates/default/shared.html
/templates/default/shared/shared.html
/templates/shared/shared.html
and none seems to be loaded at all.
It should work at least from /templates/shared/shared.html.
Please try to use latest ATK4 version from master branch from GitHub https://github.com/atk4/atk4. Current fully working version is 4.2.5.
If you start to learn ATK4 or start completely new project based on ATK4 framework, then you better look into 4.3 branch in GitHub and learn and use it. There are quite a lot of things changed in 4.3 (not yet released) version so you better use them now and you'll not need to "convert" your project from 4.2.x to 4.3 later on when 4.3 will be officially released.
I'm new to GAE, WeasyPrint and Python. I realise that WeasyPrint relies on quite a few dependences. I have had a look at the install documentation for Windows. But I cant seem to figure out how I would get it working on GAE. Is there no way to download an version with all the dependencies included and just copy it to my project folder?
Its not possible to run WeasyPrint directly on appengine. You should always read the docs on the dependencies. WeasyPrint is dependent on cairo and pango which are 'c' based libs. You can only run pure python libraries that you supply. There are some directly supported python libraries that do have some 'c' that are supported like PIL and libxml. But that isn't enough for WeasyPrint.