C:\Users\E080978\Downloads\jmagick-master\src>nmake -f Makefile.all ALL
Microsoft (R) Program Maintenance Utility Version 14.00.24234.1
Copyright (C) Microsoft Corporation. All rights reserved.
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\jmagick.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_Magick.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_MontageInfo.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_DrawInfo.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_ImageInfo.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_MagickImage.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_PixelPacket.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\obj\magick\magick_QuantizeInfo.obj
Could Not Find C:\Users\E080978\Downloads\jmagick-master\lib\jmagick.dll
Could Not Find C:\Users\E080978\Downloads\jmagick-master\lib\jmagick.exp
Could Not Find C:\Users\E080978\Downloads\jmagick-master\lib\jmagick.lib
mkdir "..\lib"
A subdirectory or file ..\lib already exists.
mkdir "..\obj\magick"
A subdirectory or file ..\obj\magick already exists.
mkdir "..\generated"
A subdirectory or file ..\generated already exists.
mkdir "..\doc"
A subdirectory or file ..\doc already exists.
"C:\Program Files\Java\jdk1.8.0_171\bin\javac" -target 1.5 -d ..\classes -classpath ..\src\magick -sourcepath ..\src\magick ..\src\magick\ClassType.java ..\src\magick\ColorspaceType.java ..\src\magick\CompositeOperator.java ..\src\magick\CompressionType.java ..\src\magick\DecorationType.java ..\src\magick\DrawInfo.java ..\src\magick\ExceptionType.java ..\src\magick\FilterType.java ..\src\magick\GeometryFlags.java ..\src\magick\GravityType.java ..\src\magick\ImageInfo.java ..\src\magick\ImageMagick.java ..\src\magick\ImageType.java ..\src\magick\InterlaceType.java ..\src\magick\InterpolatePixelMethod.java ..\src\magick\Magick.java ..\src\magick\MagickApiException.java ..\src\magick\MagickException.java ..\src\magick\MagickImage.java ..\src\magick\MagickInfo.java ..\src\magick\MagickLoader.java ..\src\magick\MagickProducer.java ..\src\magick\MapMode.java ..\src\magick\MontageInfo.java ..\src\magick\MontageMode.java ..\src\magick\NoiseType.java ..\src\magick\PaintMethod.java ..\src\magick\PixelPacket.java ..\src\magick\PreviewType.java ..\src\magick\PrimitiveType.java ..\src\magick\ProfileInfo.java ..\src\magick\QuantizeInfo.java ..\src\magick\QuantumTypes.java ..\src\magick\RenderingIntent.java ..\src\magick\ResolutionType.java ..\src\magick\SegmentInfo.java ..\src\magick\StorageType.java ..\src\magick\TimerState.java ..\src\magick\TypeMetric.java ..\src\magick\util\DisplayImageMetaData.java ..\src\magick\util\DisplayIPTCData.java ..\src\magick\util\MagickCanvas.java ..\src\magick\util\MagickViewer.java ..\src\magick\util\MagickWindow.java
javac: directory not found: ..\classes
Usage: javac <options> <source files>
use -help for a list of possible options
NMAKE : fatal error U1077: '"C:\Program Files\Java\jdk1.8.0_171\bin\javac.EXE"' : return code '0x2'
Stop.
Trying to make jmagick, using this MakeFile Source
I am trying to use nmake to compile my C and JAVA files.
I have installed VCode and VC++.
I have observed I cannot create object file(for C files) as cl gives me jni.h not found.
I do not why the error mentioned above along with "javac directory error" seems to occur.
Related
I'm attempting to take a DLL that is not strongly named and then strongly name it without needing to have the source code, since I will not always have the source code, only the DLL. When I try and run the batch file with the below code to accomplish this I get an error. Here is the code:
"C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.7.2 Tools\ildasm.exe" .\targetFile.dll /out:.\Signed\targetFile.il
"C:\Windows\Microsoft.NET\Framework\v2.0.50727\ilasm.exe" .\Signed\targetFile.il /dll /key=.\targetFile.snk /output=.\Signed\targetFile.dll
The error I get is the following:
.\Signed\targetFile.il(43) : error -- Failed to extract public key: 0x80070005
I'm not sure what I'm missing, I have permissions to all involved folders including the MacnineKeys folder in ProgramData.
I am looking for help on CATIA V5 R30 CAA help. I am getting the below error.
C:\Program Files\Dassault Systemes\B30.\BSFBuildtimeData\PublicInterfaces\CATIAV5Precompiled.h(47): fatal error C1083: Cannot open include file: 'wtypes.h': No such file or directory.
There are two reasons you are getting this error:
CAA RADE is not installed correctly. Try Check integrity from the Software Management. It will give any error if any RADE component is missing.
Missing some dependence missing from your machine. Try to build your CAA workspace using the tck batches. It will show any missing dependencies in step 3, 4 or 5:
cd "Target WS"
call "TCK_INIT.BAT" - ie. "C:\Program Files (x86)\DASSAULT SYSTEMES\B215\intel_a\code\command\TCK_INIT.BAT"
call tck_profile "CATIA Version" - i.e V6R2014_B215
call mkgetpreq -p "DS install path" - i.e "c:\Program Files\Dassault Systemes\B215"
call mkmk -W %TARGET WS% -a
Mostly, you have missing JDK or windows SDK.
the platform should be win10+vs2017, not win7+vs2017
I downloaded a solution file from PTC (Creo Parametric) for their toolkit.
They have a user guide to follow, linked below:
http://support.ptc.com/WCMS/files/172149/en/creo4_m010_Toolkit_GSG.pdf
The solution file is designed for visual studio 2015 (I am using 2017).
When I build the makefile I get the following errors:
U1077 'cl' : return code '0x1'
&
MSB3073 The command "name /f make_install dll" exited with code 2.
I am trying to figure out, what does 'cl' : return code '0x1' truly mean in this exact context?
At this stage, PTC supposedly handed everything over on a silver platter.
I did see these posts:
NMAKE : fatal error U1077: 'cc' : return code '0x1'
-seems to be compiler related, but I am using Visual Studio so this should be a mute point
fatal error U1077: 'cl' : return code '0x1' new
-The PTC user guide specifically tells me to simply load Visual Studio and open the solution file, define the load point path, and build.
The only thing I had to do special was define the following in the makefile they provided:
# PROTOOL_SRC = ../../../..
PROTOOL_SRC = C:/PTC/CREO4~1.0/M070/COMMON~1/PROTOO~1
Basically they need you to edit the makefile to define the directory of where the toolkit dependencies are installed.
Here is the part of the make file where I define PROTOOL_SRC and the compiler flags below, where 'cl' is.
# Pro/Toolkit Source & Machine Loadpoint (EXTERNAL USE - DEFAULT)
# PROTOOL_SRC = ../../../..
PROTOOL_SRC = C:/PTC/CREO4~1.0/M070/COMMON~1/PROTOO~1
PROTOOL_SYS = $(PROTOOL_SRC)/$(PRO_MACHINE_TYPE)
# Pro/Toolkit Source & Machine Loadpoint (PTC INTERNAL USE)
#PROTOOL_SRC = $(PTCSRC)/protoolkit
#PROTOOL_SYS = $(PTCSYS)
ICU_PATH = $(PROTOOL_SYS)/obj
# Include File Paths
INCS = -I. -I$(PROTOOL_SRC)/protk_appls/includes
-I$(PROTOOL_SRC)/includes
# Compiler Flags
CC = cl
MACH = -DPRO_MACHINE=36 -DPRO_OS=4
CCFLAGS = -c -GS -fp:precise -D_WSTDIO_DEFINED -D_USING_V110_SDK71_
CFLAGS = $(CCFLAGS) $(INCS) $(MACH)
So, knowing all of this.. why would the makefile error 'cl' : return code '0x1' exist?
Is there something I need to set in my Visual Studio 2017 Environment?
I'm new to the subject of windows drivers. I'm trying to build one of the Windows-driver-samples in Visual Studio 2015. The compilation and linking steps pass without errors and then I get the following error:
TRACKER : error TRK0002: Failed to execute command:
""C:\Program Files (x86)\Windows Kits\10\bin\x86\inf2cat.exe"
/os:10_x64 /driver:x64\Debug\WFPSamplerCalloutDriver\".
The operation identifier is not valid.
(Note the relative path in /driver argument). If I call Inf2Cat manually from command prompt with full path to the driver, it passes without a hitch:
C:\Program Files (x86)\Windows Kits\10\bin\x86>Inf2Cat.exe /os:10_x64
/driver:C:\Users\****\Windows-driver-samples\network\trans\WFPSampler\sys\x64\Debug\W
FPSamplerCalloutDriver
...........................
Signability test complete.
Errors:
None
Warnings:
None
Catalog generation complete.
C:\Users\****\Windows-driver-samples\network\trans\WFPSampler\sys\x64\Debug
\WFPSamplerCalloutDriver\wfpsamplercalloutdriver.cat
So, it seems to me that VS somehow failed to provide the full path to the driver in the argument to Inf2Cat.
How can I fix this? Which configuration property of my project is incorrect?
Description
Seems Inf2Cat from SDK10 does not accept directory path format provided by VS Project Configurator. Works when: either output folder name has with no trailing "\" or folder name ends up with "\.".
Workaroud
Disable Inf2Cat under Project Preferences: Run Inf2Cat -> No
Configure build events under Build-Events->Post Build-Event: Command Line -> "$(WindowsSdkDir)bin\$(DDKPlatform)\inf2cat.exe" /os:10_$(DDKPlatform) /driver:"$(ProjectDir)$(IntDir)$(MSBuildProjectName)"
I followed all the instruction mentioned in https://github.com/cisco/openh264 but I am unable to get through. The information is cited in link but its quite confusing.
Alternative Way:
You can build Openh264 using visual studio in windows. Here are the steps..
i) Download OpenH264 source code provided by cisco (that already you
mentioned https://github.com/cisco/openh264).
ii) Now you will find two visual studio compatible projects in
directory /OpenH264/codec/build/win32/dec and
/OpenH264/codec/build/win32/enc.
iii) You will need to download NASM software from http://www.nasm.us/pub/nasm/releasebuilds/2.12.02/
iv) Install NASM software on the directory C:\NASM or wherever you like.
v) Then Add NASM executable path to all these visual studio projects.
vi) Then You can either select static or dynamic library in general
options.
vi) If you are able to perform all these operations successfully, you will have 5 different .lib or .dll files named welsdcore, welsdecplus, welsecore, welsencplus, welsvp and those
are usable in any visual studio projects.
Now if you want to get openh264 features, just add all these libraries to your project and enjoy.
Hope it will help you.. :)
I also had some difficulty building openh264 on Windows using the recommended mingw approach.
In my case make crashed for all configurations I tried:
bash -c "make OS=msvc ARCH=x86_64 USE_ASM=No BUILDTYPE=Debug clean"
bash -c "make OS=msvc ARCH=x86_64 USE_ASM=No BUILDTYPE=Debug"
0 [main] make 3888 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
564 [main] make 3888 open_stackdumpfile: Dumping stack trace to make.exe.stackdump
0 [main] make 5448 handle_exceptions: Exception: STATUS_ACCESS_VIOLATION
561 [main] make 5448 open_stackdumpfile: Dumping stack trace to make.exe.stackdump
copying dll files to destination folder...
FullDestDir is E:\projects\openh264\bin\x64\Debug
current dir is:
E:\projects\openh264
DestDir is bin/x64/Debug
cp: cannot stat `openh264.dll': No such file or directory
cp: cannot stat `openh264.lib': No such file or directory
cp: cannot stat `openh264.pdb': No such file or directory
cp: cannot stat `codec_unittest.exe': No such file or directory
cp: cannot stat `h264enc.exe': No such file or directory
cp: cannot stat `h264dec.exe': No such file or directory
BuildDebugFlag =1
BuildReleaseFlag =0
BuildDebugInfo ="build debug--failed"
BuildReleaseInfo =NULL
aBuildFlagList is 1 0
ReturnCode is 1
I resorted to converting the existing solution/projects (VS2008) to VS2013 and linking/building with the created .lib files.
You can find the solutions in {openh264_dir}\codec\build\win32\enc and {openh264_dir}\codec\build\win32\dec.
Building the solution will create .libs and .dlls in {openh264_dir}\bin\Win32\Release
To link to the lib, you need to link to welsenc.lib.
When running, you need to have both the welsenc.dll and welsvp.dll in your application directory. So far it seems to have worked fine for my usage.
I'm assuming that building the decoder will be similar.