In the instruction (http://pylonshq.com/docs/en/1.0/upgrading/) I find :
To upgrade to 1.0, first upgrade your
project to 0.10. This is a Pylons
release that is fully
backwards-compatible with 0.9.7.
However under 0.10 a variety of
warnings will be issued about the
various things that need to be changed
before upgrading to 1.0.
What warnings? The ones from easy_install? I get this from easy_install (I have cut away some stuff I know is not warnings).
easy_install -U http://pylonshq.com/download/0.10/Pylons-0.10.tar.gz
Downloading http://pylonshq.com/download/0.10/Pylons-0.10.tar.gz
Processing Pylons-0.10.tar.gz
Running Pylons-0.10/setup.py -q bdist_egg --dist-dir /tmp/easy_install-mGVgCf/Pylons-0.10/egg-dist-tmp-H1Lklt
warning: no previously-included files matching '*' found under directory 'tests/test_units/session'
warning: no previously-included files matching '.DS_Store' found anywhere in distribution
warning: no previously-included files matching '*.hgignore' found anywhere in distribution
warning: no previously-included files matching '*.hgtags' found anywhere in distribution
If these are the warnings the instruction talks about I need some help understanding them. What do they mean?
If these are not the warnings the instruction talks about I need some directions. When will I get these warnings the instruction talks about?
Thank you in advance.
These warnings only saying that the during Pylons upgrade (not your application) "easy_install" found some files that were in the previous distribution of Pylons (in directory) and which are not included in new package.
For example ".DS_Store" is a hidden file created by MacOSX to store some attributes (http://en.wikipedia.org/wiki/.DS_Store) and probably it was not created during installation.
Warnings mentioned in the documentation, are warnings that appear on the console when you start your application with a new Pylons and there you should look for upgrade hints (for example information about depreciations).
I think that ones are meaningless for your upgrade process.
Hope it helps...
I implemented unit and function tests according to the testing chapter in the Pylons book. During this process I found all things that I needed to change after the upgrade to 0.10.
So there are two ways of finding all warnings that need to be dealt with after upgrading to 0.10 and before upgrading to Pylons 1.0.
Start a paster server and manually surf your pylons app looking for warnings in the paster output.
Be smart and create your unit and function tests according to the Pylons book and run them to find all warnings.
Related
I keep trying different tutorials, but they all seem to be scattered and out dated.
Everyone that I am trying I am running into many errors or deprecated code.
Are there any newer tutorials or modules I can use to simplify this process?
Currently I am using electron-simple-updater, but with this I keep getting the error in the .app file that it can't find the require module. It finds it when i just run npm run electron though.
Also when I distribute the update, should it be in the .app file or the built -dist folder?
I'm trying to use libffi in one of my projects, but I can't seem to compile for iOS (or macOS, for that matter). Here is one of the various errors I've encountered while building for the iOS Simulator:
bash: src/arm/gentramp.sh: No such file or directory
Update 1: Since the question remains unanswered, I've decided to open an issue at the official repository as well.
Update 2: Question has been answered and the issue has been closed!
If you check the repository you will see that the file you require was deleted in this commit. You can find the last version of this file here.
generate-darwin-source-and-headers.py and the libffi.xcodeproj need to be updated to include all currently relevant source files.
The gentramp.sh script is not needed anymore and the current upstream xcodeproj is not up to date either with compilation settings and to be included source files for 64-bit on iOS. A patched fork can be found at https://github.com/ksjogo/libffi
sh autogen.sh
python generate-darwin-source-and-headers.py --only-ios
open libffi.xcodeproj
select scheme libffi-iOS and device Generic iOS Device
click "Product - Build"
If success, you would see a "Product/libffi.a" in the side bar, you can right click it to get the lib in the finder.
Please make sure you are following the installing libffi instructions released on the TBD or git project: https://github.com/libffi/libffi
Here some of the main Highlights:
First you must configure the distribution for your particular
system. Go to the directory you wish to build libffi in and run the
"configure" program found in the root directory of the libffi source
distribution.
If you're building libffi directly from version control, configure won't
exist yet; run ./autogen.sh first.
You may want to tell configure where to install the libffi library and
header files. To do that, use the --prefix configure switch. Libffi
will install under /usr/local by default.
If you want to enable extra run-time debugging checks use the the
--enable-debug configure switch. This is useful when your program dies
mysteriously while using libffi.
Another useful configure switch is --enable-purify-safety. Using this
will add some extra code which will suppress certain warnings when you
are using Purify with libffi. Only use this switch when using
Purify, as it will slow down the library.
For iOS builds, the 'libffi.xcodeproj' Xcode project is available.
Configure has many other options. Use "configure --help" to see them all.
Once configure has finished, type "make". Note that you must be using
GNU make. You can ftp GNU make from ftp.gnu.org:/pub/gnu/make .
To ensure that libffi is working as advertised, type "make check".
This will require that you have DejaGNU installed.
To install the library and header files, type "make install".
Alternatively, try merging one of the following git projects to your project in order to include the missing files. Please make sure the files are not outdated before merging.
1 https://github.com/pandamonia/libffi-iOS
2 https://github.com/influitive/libffi-iOS
3 https://github.com/landonf/libffi-ios
This is my first time trying with Gstreamer for ios , I went with the tutorial and installed the SDK with the link provided by the tutorial:
http://docs.gstreamer.com/display/GstSDK/Installing+for+iOS+development
The installation works fine, but after I start trying the tutorial example projects, there couple of compiling errors compiling about missing gst/video/videooverlay.h . Then I looked into the header folder under the installed GStreamer header folder, there is no filed called video/videooverlay.h
Then I search online, found this information:
Gstreamer for iOS provided is out of date. I used the freedesktop packages
from https://github.com/braincorp/gstreamer_ios_tutorial
Then I downloaded another installation pkg for GStreamer
Then while I was trying to install the later version, the installer give me error saying:
you cannot install GStreamer 1.0 (Development Files) in this location.
Then I thought I might need to uninstall the previous version, but I couldn't finder a standard uninstallation option from the installer, then I searched online, find one post suggest remove the GStreamer folder under ~/Library/Developer
I have removed the installed folder, so I don't have any header files, but the new installer still gives the same error
I have been trying to figure this out for sometime, couldn't find useful info on line , I really appreicate any clue and help you might have!
Thanks!!
Jing
Answering my own question here..
not sure what's the issue, after restarting my mac, and run the installer couple of times with the same error, it suddenly worked ....... i am not sure what's the matter here, hope gstreamer team can improve the stability of the installer in the future.
At work we are currently trying to get the IOS tutorials from the streamer 1.0 sdk to run.
1) Compilation: Same thing: we managed to bootstrap (cerbero ... bootstrap) and compile (cerebra ... package streamer-sdk) using the official cerebero git repository.
But:
a) We had to mock around with the /cerbero/cerbero/enums.py file:
Add in the collection of supported old IOS (6.0, 6.1, 7.0, etc...) the one corresponding to our Xcode version : IOS 8.4
b) We had to customize the /cerbero/config/ios.config and iOS-universal.config files to get them to use the right architecture in our case: arm7v or arm7 instead of X64_86 or x86
c) We removed the not found is_asm() function from the x264 plugin's recipe file in the /cerbero/recipes.
For a reason we ignore, for all other platforms but IOS, the recipes check on the architecture available using:
if self.config.target_arch == Architecture.xxx:
of iOS is was using that missing function: is_asm(self.config.target_arch)
We replaced it by:
if self.config.target_arch == Architecture.ARMv7:
Compiling an iOS app using streamer:
So far it is a failure. we bumped into the same missing overlay.h header file. We couldn't find it anywhere.
DIFFERENCE between gstreamer.com (the sdk provider) and the official streamer website (free desktop.gsteamer.org):
We found out that gstreamer.com is clearly a commercial goal company that is making available the sdk, that people struggle on with for IOS (tested and working fine on linux) and the official website is providing the gstreamer library only without an sdk.
So this is what we are trying to use instead as of today.
Versions infos:
sdk (from gstreamer.com): current cerbero git master branch: git clone git://anongit.freedesktop.org/gstreamer-sdk/cerbero
official gstreamer library:
http://gstreamer.freedesktop.org/data/pkg/ios/1.5.2/
I am new to rebar and try to create a demo app to understand the flow.
I have downloaded rebar & ran bootstrap.
I created a project according to this manual:
justenough-otp1
when I run the compile it compiles all the files and when it runs it.
when i try to generate the app it gives me the following error:
WARN: 'generate' command does not apply to directory /users/olive/poznov/Downloads/rebar-master/learn/apps
Command 'generate' not understood or not applicable
i tried to run
./rebar generate
from both the parent folder and apps folder (of course changing the path in the rebar.config file)
any ideas what might cause the problem?
The generate command is used to build a release. It is much more than a simple application: it contains the VM, your application and all the libraries and dependencies needed. So it needs some more information to be generated. You can look at Erlang rebar tutorial: generating releases and upgrades or LYSE release with reltool for more information (learning from the Eralang documentation is much more difficult)
I am getting the following error:
I am not sure why.
It looks like you have an old MetroWerks CodeWarrior (that's what the __MWEKRS__ macro signifies) include directory in your search path. Did you import this project from an old CodeWarrior project ? Or did you inadvertently add an inappropriate directory somehow ? Look at the build commands being generated, in particular at what -I directives are being emitted.