Sysprogs forums › Forums › VisualGDB › VisualGDB raspberry pi errors
- This topic has 3 replies, 3 voices, and was last updated 10 years, 1 month ago by support.
-
AuthorPosts
-
October 19, 2014 at 21:56 #909kelseybekkParticipant
I am trying to get VisualGDB set up with Visual Studio 2010 set up so that it can talk to my raspberry pi. However when I build the project from this tutorial: http://visualgdb.com/tutorials/raspberry/crosscompiler/. I get the errors:
1>
Build started: Project: LinuxHelloWorld, Configuration: Debug Win32
1> VisualGDB: Attempting inline build…
1> VisualGDB: Run “cmd.exe /c “C:SysGCCraspberrybinmake.exe” CONFIG=Debug” in directory “C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorld” on local computer
1> make: *** No targets specified and no makefile found. Stop.
1>1> Command exited with code 2
1> Executable: cmd.exe
1> Arguments: /c “C:SysGCCraspberrybinmake.exe” CONFIG=Debug
1> Directory: C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorld
1>VisualGDB : error : Command-line action failed
1>C:Program Files (x86)MSBuildMicrosoft.Cppv4.0V110Microsoft.MakeFile.Targets(38,5): error MSB3073: The command “”C:Program Files (x86)SysprogsVisualGDBVisualGDB.exe” /build “C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorldLinuxHelloWorld.vcxproj” “/solution:C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorld.sln” “/config:Debug” “/platform:Win32″” exited with code 1.
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========I do not understand the errors, let alone how to go about fixing them. Thanks ahead of time!
October 20, 2014 at 17:01 #3384supportKeymasterHi,
It looks like the C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorld directory is missing the ‘Makefile’ file that is required to build your project. Normally it is generated by the wizard. Can you try creating another project? Is Makefile generated then?
October 21, 2014 at 00:11 #3385AnonymousParticipantIt did create a Makefile. It’s below. Also, I did try to make another project and it creates the same error.
ifeq ($(IS_LINUX_PROJECT),1)
RPATH_PREFIX := -Wl,–rpath=’$$ORIGIN/../
LIBRARY_LDFLAGS += $(EXTERNAL_LIBS)
LIBRARY_LDFLAGS += -Wl,–rpath=’$$ORIGIN’
LIBRARY_LDFLAGS += $(addsuffix ‘,$(addprefix $(RPATH_PREFIX),$(dir $(EXTERNAL_LIBS))))ifeq ($(TARGETTYPE),SHARED)
LIBRARY_LDFLAGS += -Wl,-soname,$(TARGETNAME)
endifelse
LIBRARY_LDFLAGS += $(EXTERNAL_LIBS)
endifLIBRARY_LDFLAGS += $(ADDITIONAL_LINKER_INPUTS)
all_make_files := Makefile $(CONFIGURATION_FLAGS_FILE) $(ADDITIONAL_MAKE_FILES)
ifeq ($(STARTUPFILES),)
all_source_files := $(SOURCEFILES)
else
all_source_files := $(STARTUPFILES) $(filter-out $(STARTUPFILES),$(SOURCEFILES))
endifsource_obj1 := $(all_source_files:.cpp=.o)
source_obj2 := $(source_obj1:.c=.o)
source_obj3 := $(source_obj2:.s=.o)
source_objs := $(source_obj3:.S=.o)all_objs := $(addprefix $(BINARYDIR)/, $(notdir $(source_objs)))
ifeq ($(GENERATE_BIN_FILE),1)
all: $(BINARYDIR)/$(basename $(TARGETNAME)).bin$(BINARYDIR)/$(basename $(TARGETNAME)).bin: $(BINARYDIR)/$(TARGETNAME)
$(OBJCOPY) -O binary $< $@ else
all: $(BINARYDIR)/$(TARGETNAME)
endififeq ($(TARGETTYPE),APP)
$(BINARYDIR)/$(TARGETNAME): $(all_objs) $(EXTERNAL_LIBS)
$(LD) -o $@ $(LDFLAGS) $(START_GROUP) $(all_objs) $(LIBRARY_LDFLAGS) $(END_GROUP)
endififeq ($(TARGETTYPE),SHARED)
$(BINARYDIR)/$(TARGETNAME): $(all_objs) $(EXTERNAL_LIBS)
$(LD) -shared -o $@ $(LDFLAGS) $(START_GROUP) $(all_objs) $(LIBRARY_LDFLAGS) $(END_GROUP)
endififeq ($(TARGETTYPE),STATIC)
$(BINARYDIR)/$(TARGETNAME): $(all_objs)
$(AR) -r $@ $^
endif-include $(all_objs:.o=.dep)
clean:
ifeq ($(USE_DEL_TO_CLEAN),1)
del /S /Q $(BINARYDIR)
else
rm -rf $(BINARYDIR)
endif$(BINARYDIR):
mkdir $(BINARYDIR)#VisualGDB: FileSpecificTemplates #<--- VisualGDB will use the following lines to define rules for source files in subdirectories
$(BINARYDIR)/%.o : %.cpp $(all_make_files) |$(BINARYDIR)
$(CXX) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep) $(BINARYDIR)/%.o : %.c $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep) $(BINARYDIR)/%.o : %.S $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) $(ASFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep) $(BINARYDIR)/%.o : %.s $(all_make_files) |$(BINARYDIR)
$(CC) $(CFLAGS) $(ASFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep) #VisualGDB: GeneratedRules #<--- All lines below are auto-generated
$(BINARYDIR)/Component.o : Omx/Component.cpp $(all_make_files) |$(BINARYDIR)
$(CXX) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)
$(BINARYDIR)/ComponentPort.o : Omx/ComponentPort.cpp $(all_make_files) |$(BINARYDIR)
$(CXX) $(CXXFLAGS) -c $< -o $@ -MD -MF $(@:.o=.dep)October 21, 2014 at 00:23 #3386supportKeymasterHi,
That is very strange. What happens if you start Command Prompt and manually run the following commands:
cd /d C:UsersKelsARCommLinuxHelloWorldLinuxHelloWorld "C:SysGCCraspberrybinmake.exe" CONFIG=Debug type Makefile
Does Make still complain about a missing Makefile? Does your source directory have some non-typical access rights? What happens if you try setting the access to the current user to ‘full control’?
-
AuthorPosts
- You must be logged in to reply to this topic.