no rule to process file of type image.png for architecture i386 - objective-c

I.m trying to create Pod for Cocoapods. And during podspec validation got this error:
- ERROR | [iOS] xcodebuild: Returned an unsuccessful exit code.
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/myfiles.png' of type image.png for architecture i386
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/nav_clear_pixel.png' of type image.png for architecture i386
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/nav_pixel.png' of type image.png for architecture i386
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/samplefiles.png' of type image.png for architecture i386
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/myfiles.png' of type image.png for architecture x86_64
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/nav_clear_pixel.png' of type image.png for architecture x86_64
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/nav_pixel.png' of type image.png for architecture x86_64
- NOTE | xcodebuild: warning: no rule to process file 'sequencing-file-selector-api-objc/Pod/ResourceBundle.bundle/samplefiles.png' of type image.png for architecture x86_64
- NOTE | [iOS] xcodebuild: : error: Not enough arguments provided; where is the input document to operate on?
Podspec contains following settings:
s.resource = 'Pod/ResourceBundle.bundle'
s.resources = ['Pod/ResourceBundle.bundle/*.png']
All images are within ResourceBundle.bundle file
How to handle such error? Can't validate podspec.

As I found out the problem was that I did'n specified resources files as a actually Resources (.png, .storyboard, and .xib) while creating CocoaPod.
So I created a Resources folder within the pod and moved all png images, custom storyboard file and xib files.
In podspec file I added following specification:
s.resources = ['Resources/**/*.*']
As a result podspec file was validated successfully and I was able to release the pod.

Related

Error in Compiling DLPC3010 DLPC-API in jetson Nano

I am trying to compile DLPC Projector APIs in the jetson nano. However, it is throwing an error as in added snapshot. I came across one solution here. However it is not being helpful.
DLPC-APS - https://www.ti.com/tool/DLPC-API
ig#ig-desktop:~/Desktop/Texas Instruments/DLPC-API-1.8/samples/dlpc654x_samples/build$ cmake ../
-- Configuring done
-- Generating done
-- Build files have been written to: /home/ig/Desktop/Texas Instruments/DLPC-API-1.8/samples/dlpc654x_samples/build
ig#ig-desktop:~/Desktop/Texas Instruments/DLPC-API-1.8/samples/dlpc654x_samples/build$ make
[ 4%] Building C object CMakeFiles/libdlpc654x_sample.dir/home/ig/Desktop/Texas_Instruments/DLPC-API-1.8/api/dlpc_common.c.o
cc: error: unrecognized command line option ‘-m32’
CMakeFiles/libdlpc654x_sample.dir/build.make:75: recipe for target 'CMakeFiles/libdlpc654x_sample.dir/home/ig/Desktop/Texas_Instruments/DLPC-API-1.8/api/dlpc_common.c.o' failed
make[2]: *** [CMakeFiles/libdlpc654x_sample.dir/home/ig/Desktop/Texas_Instruments/DLPC-API-1.8/api/dlpc_common.c.o] Error 1
CMakeFiles/Makefile2:88: recipe for target 'CMakeFiles/libdlpc654x_sample.dir/all' failed

fatal error: openssl/bio.h: No such file or directory in Yocto

My Yocto sources are on Warrior currently and I am in a process of migrating them to dunfell so I cloned all the required layers for dunfell branch including meta-swupdate.
Now, I am trying to generate swupdate image by bitbake swupdate-image command for dunfell and I am getting errors as given below:
.
.
In file included from /home/panther2/dunfell/build/tmp/work/corei7-64-poky-linux/swupdate/2021.04-r0/git/corelib/verify_signature.c:15:
/home/panther2/dunfell/build/tmp/work/corei7-64-poky-linux/swupdate/2021.04-r0/git/include/sslapi.h:31:10: fatal error: openssl/bio.h: No such file or directory
31 | #include <openssl/bio.h>
| ^~~~~~~~~~~~~~~
compilation terminated.
.
.
make[2]: *** [core/swupdate.o] Error 1
/home/panther2/dunfell/build/tmp/work/corei7-64-poky-linux/swupdate/2021.04-r0/git/mongoose/mongoose.c:4473:10: fatal error: openssl/ssl.h: No such file or directory
4473 | #include <openssl/ssl.h>
| ^~~~~~~~~~~~~~~
compilation terminated.
.
.
Looks like it is unable to find ssl related header files. Any lead on this?
There is no openssl dependency in the swupdate recipe.
Adding DEPENDS += "openssl" in a swupdate_%.bbappend file helps.

Titanium Hyperloop app does not compile due to too small libhyperloop.a lib file

I can't compile my titanium + hyperloop application. The compiler complains about the filesize of my libhyperloop.a, which is 2 bytes. Does this mean the file is corrupt, and does someone knows a workaround? I have inspected the file in both hyperloop 1.1.0 and 1.2.0 and both have the same file size.
ld: file too small (length=2) file '/Users/david/Projects/app/modules/iphone/hyperloop/1.1.0/libhyperloop.a' for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Can it be that my libhyperloop.a is corrupt? And does someone knows where to obtain a fully functional version of the hyperloop module?

Bazel Build Mnist Serving Interface Fail on OSX El Capitan

I'm trying to build the TensorFlow serving basic tutorial on OSX El Capitan but run into this error. Any ideas?
Here's the link to the tutorial: https://tensorflow.github.io/serving/serving_basic
$ bazel build //tensorflow_serving/example:mnist_inference
INFO: Found 1 target...
ERROR: /Users/robertgrzesik/Documents/Development/TensorFlow/serving/tensorflow_serving/example/BUILD:53:1: Linking of rule '//tensorflow_serving/example:mnist_inference' failed: osx_gcc_wrapper.sh failed: error executing command external/bazel_tools/tools/cpp/osx_gcc_wrapper.sh -o bazel-out/local_darwin-fastbuild/bin/tensorflow_serving/example/mnist_inference ... (remaining 512 argument(s) skipped): com.google.devtools.build.lib.shell.BadExitStatusException: Process exited with status 1.
clang: warning: argument unused during compilation: '-pthread'
ld: warning: option -noall_load is obsolete and being ignored
ld: warning: option -noall_load is obsolete and being ignored
ld: warning: option -noall_load is obsolete and being ignored
ld: warning: option -noall_load is obsolete and being ignored
ld: warning: option -noall_load is obsolete and being ignored
ld: warning: option -noall_load is obsolete and being ignored
This change was also made to my WORKSPACE file (based on this discussion):
git_repository(
name = "boringssl_git",
commit = "32bfe16a53ad13523eadce08dd2f835bc2b0b52d",
init_submodules = True,
remote = "https://github.com/ctiller/boringssl-bazel",
)
Found a temporary fix to use docker. Seems like there are known issues with OSX right now.
Docker install instructions can be found here: http://tensorflow.github.io/serving/docker

j2objc Compile error: Undefined symbols for architecture arm64:

i get the following error when i run j2objcc -o blssmibi BLSSMIBI.o
Undefined symbols for architecture x86_64:
"_OBJC_CLASS_$_Curve", referenced from:
objc-class-ref in BLSSMIBI.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
what should i do to fix this?
There's no Curve class anywhere in j2objc's libraries, so my guess it's a dependency from the Java file that you used to generate BLSSMIBI (maybe that's the it looks like a package prefix was used). If you aren't sure what a class's dependencies are, try compiling with javac to a temporary directory and see what name.class files are created (ignore the ones with $ in their names, as they're inner classes). That list of class files is used to figure out all the classes that need transpiling, as well as all the .o files that the app requires.